Hi Stoyan, This thread is (was? ;) about IPC. Most of the features you and Kamen are longing for in Indigo aren't quite as relevant for simple IPC...
My advice to the original poster stands: grab a shared-source wrapper for shared memory, and use that to marshal data back and forth between processes. For true RPC (remote, across machine boundaries)? I like HttpWebRequest for the internet, and a good Named Pipes wrapper for the intranet. -S On Tue, 18 Nov 2003 13:58:21 +0200, Stoyan Damov <[EMAIL PROTECTED]> wrote: >>> I'd much prefer an explicit model of messaging for IPC, something >like:.... >>> That's explicit -- clear to any reader of the code -- and hey look, it's >not much more typing than Remoting! ... > >Shawn, >I support you 1000%, but what am I supposed to do before Indigo ships (I >mean its 3rd release)? (Pre)(Re)invent it?:( > >Cheers, >Stoyan > >=================================== >This list is hosted by DevelopMentor� http://www.develop.com >Some .NET courses you may be interested in: > >Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles >http://www.develop.com/courses/gaspdotnet > >Guerrilla .NET, 8 Dec 2003, in Los Angeles >http://www.develop.com/courses/gdotnet > >View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Guerrilla ASP.NET, 10 Nov 2003 in London and 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnet Guerrilla .NET, 8 Dec 2003, in Los Angeles http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
