The performance should not be very different for that kind of application. Using a socket has the advantage of allowing easy remote administration to your service over standard protocol.
Note that you could also build your administration program into your service and use a browser as administrative tool. Just use THttpServer (Or even HTTPS) and write a web application to manage your service ! Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Monday, May 15, 2006 6:22 PM Subject: [twsocket] IPC - TWSocket or Named Pipes? > Hi, > > I need to rewrite an interactive service since interactive > services are no longer supported in Vista ;( I want to split > it into two parts, GUI and service application. The service > in question needs to be controlled locally only. What do > you suggest as the IPC protocol, TWSocket or named pipes? > Currently TWSocket appears to be an easy implementation, > but is it as fast as named pipes? > > --- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
