Posts filed under ‘WCF/Indigo’
Took the plung today and installed the x64 version of Windows Vista (build 5308) on my machine. I had a spare 3 GB of disk space that I thought would be enough.. 10 mins later I was running Acronis disk manager from CD (nobody appears to have Partition management software for Windows XP Pro x64) to steal some space from another partiton. I needed a min of 11 GB of disk space to install Vista.
The new approach by Microsoft to produce regular updates to their Customer Technology Previews (CTPs) is much needed. No longer do we have to wait months (or years) between releases to find code that we have developed left limping along or just plain hosed – a gibbering wreck due to namespace or library changes…
PerPixelOpacity allows for non-regular shapes – allowing all sorts of groovy things.
Lester (msdn blogger) illustrates how to use it to create an unique splash screen here.
Watch out for the WinFX Feb Uninstall tool. It can turn Visual Studio 2005 into a gibbering wreck…
You’ll need to remove previous versions of WinFX before installing – MS have released a tool to make things painless here.
Now if I could only get invited to the Vista Feb CTP due out today…
Like most adHoc implementations – the communication mechanism in the original design wasn’t up to scratch. The communication mechanism has to fulfil the following requirements:
- logical groups of peered agents (ala fully trusted agents – or agents who are friends),
- local agents who bias the information exchange with an element of caution (agents who are acquaintances)
- agent communication with that should be treated with caution (agents who are strangers)
- Primary Process agent communication
- This dialog should be isolated, allowing the Primary to steer agents to some degree, allow information to be extracted about agent performance, direction, decision paths. Finally agents datasets (both decision paths, data and generated code) should be consumed and integrated with the Primary process (using e-Change).
- The communication channel should be clearly defined – using a contract approach
- The channel should be loose – allowing disconnected processing (agents can be local or remote and defined by the agent instance engine under direction of the Primary Process)
- The communication channel should allow reflexive discovery – allowing both parties to disover something about the nature of the channel. The channel in this environment isn’t just a conduit – it’s also a mechanism to provide directional indicators allowing the agent to discover and explore it’s assigned dataset (see above for an overview of the dataset).
With this in mind – it was time for a review and redesign of the mechanism.
After some investigation of the options – I’ve decided to start using part of the Windows Communication Framework. Initial trails show that it will provide a significant improvement over what is in place at the moment and should allow the system to grow and perform better.