I would go with RCF, most of the complexities are abstracted away so it's pretty easy, and plus it is free.
http://www.deltavsoft.com/ From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Jano Petras Sent: Tuesday, 22 November 2011 6:53 PM To: ozDotNet Subject: Re: Client /Server alternative for TCP Well, hosting you application under IIS would get rid of worries regarding listeners and connections, if your system needs to follow regular REST request/response pattern (that is, you don't need to keep the connection open). WCF is an option here as it supports REST, or - just plain ASP.NET or MVC with some good REST library if you don't need all the bells and whistles WCF provides. My 2 cents, jano On 18 November 2011 07:05, Anthony Mayan <ifum...@gmail.com> wrote: Currently looking at building a client server app but thinking whether we should use TCP. Could we we use rest service instead or another method? Want to avoid creating a multi-thread tcp listener to handle all the connections...anyone have an suggestions? Anthony
