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. Ben > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED]]On Behalf Of Philip Nelson > Sent: Sunday, 19 January 2003 10:50 PM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] Remoting: What is everybody doing for > simple, robust, secure, efficient IPC? > > > > 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 . > > When you use a connection to localhost, 127.0.0.1, it's no longer > on the wire, > correct? So if you limit listening to localhost you would have > garaunteed both > real ipc and no network access to your channel. I have an > unproven assumption > that ipc would be faster using tcp than using COM, though it is a > reasonable > suggestion. If both statements are true, you'd be hard pressed > to choose COM > over tcp when you facter in all the extraneous issues COM brings > into a .net > project. I tend to feel the same way about Named pipes, though > ignorance has a > lot to do with my feelings there. Named pipes between machines > have been the > source of soooo many network problems for me. > > 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.
