Want to avoid creating a multi-thread tcp listener to handle all the connections...anyone have an suggestions?
Assuming you want duplex communication ... if you plan to run inside the LAN where Remoting can open callback channels, the Remoting is old but reliable. A singleton server handles incoming requests on different threads automatically. I've used this technique in a few apps and it's easy to code (once you get over the initial hump). It's not scalable outside the LAN of course, and to overcome that we had to buy Genuine Channels so duplex communication happens on a single port. These days I would use WCF over TCP with callbacks. If you just want a dumb one-way service then I'd use basicHttpBinding WCF. If you want something dumb and "open" then I'd use ASMX or REST. Greg
