I integrated this spectacular messaging API into the ASP.NET web server and I have it loaded in the background doing message passing. I wrote a little demo and have had ten instances of it running on the concurrent thread. I just wanted to see if it could handle a serious number of daemons at the same time.
The file mapping IOStream was faster than the Mailslots on the same machine and performance was superb with it mapped into the virtual memory space. (That's where Windows pretends it is a file when in fact it is being referenced from RAM, making it asynchronous for all participating clients. This same mechanism is supported in Linux and FreeBSD.)
I have taken a stab at the horizontal ticker tape marquee and had it printing a series of messages from the server in real time, it looks pretty good. I worked on this last year but back then I was running it off mailslots.
So I'm up to my proof of concept in ASP.NET one week after going off my ANSI C version. I'd say I'm doing good for end of February.
I do have to adjust the requirements for plug-in daemons. It looks now like they would best be implemented as complementary programs in .NET 2.0 instead of a scripting language. I will probably write a daemon for all the major protocols so almost all the notable ones will be supported in Vault-OS in short order.