You shouldn't need to use sockets ( what if there is no IP stack) , .NET object are COM/COM+ objects which are very advanced forms of IPC.
For more info see the Microsoft.ComServices namespace , here is a start. http://www.csharphelp.com/archives/archive116.html. Disclaimer I am no expert on this , but Word and Excel have been using this since office was first released (COM was an enhancement of DDE) which is way before network stacks became common. Ben PS : On Unix people often use sockets as is easy...same for java , the recomendation is generally to use sockets for communicating to a process on the same machine to avoid the hassle and overhead of Corba / RMI . It is the same in .NET ,setting up remoting using sockets is trivial . > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED]]On Behalf Of Shawn A. Van > Ness > Sent: Saturday, 18 January 2003 11:03 AM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] Remoting: What is everybody doing for > simple, robust, secure, efficient IPC? > > > Maybe... but I'd prefer a true local-only solution, so that I > don't have to endure the security liability of listening on a > network endpoint. > > I can't believe .NET is leading so many folks to use TCP for what > would be interprocess comm purposes... scares the heck out of me, > quite frankly. > -S > > > On Fri, 17 Jan 2003 11:22:15 -0800, Howard Hoffman > <[EMAIL PROTECTED]> wrote: > > >Doesn't Named-Pipe transport w/in machine get implemented by Win32 as > >memory-mapped file (i.e. shared memory)? > > > >You can read messages from the Advanced DOTNET archive, > unsubscribe from Advanced DOTNET, or > >subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the Advanced DOTNET archive, > unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.