There is also the question of how much overhead a TCP connection imposes. Even localhost, and even not hirtting the wire - will the stream not be encoded into TCP packets?
Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) > -----Original Message----- > From: Ben Kloosterman [mailto:[EMAIL PROTECTED]] > Sent: Sunday, January 19, 2003 4:20 PM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] Remoting: What is everybody > doing for simple, robust, secure, efficient IPC? > > > I agree with you , I would use IP sockets / remoting as it is > probably faster than COM. I was replying to Shawns comment > and stated some options. > > Shawn said > " > 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." > > 2 things to note though > > 1. Some machines dont have an Ip stack or a NIC. > 2. Some drivers have been known to do silly things with > 127.0.0.1. In addition if the program goes on a secure server > you may still have to open the port , depending on the > firewall software. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
