I forget to say that to support a few thousand simultaneous client, it is likely that yu should pour TWSocketServer code into a thread to service, let's say, 500 client per thread. And you should probably NOT use the main thread to run TWSocketServer code.
Be aware that ICS is asynchronous and it will multitask (cooperatively) nicely within a thread and serve a lot of connections in a single thread. But this is not infinite : Windows has his limits (Nothing in ICS limit the number of connections nor the number of threads). If you are used with some other socket component, you should probably forget everything you know. ICS has a totally and unique programming model. What is good for a synchronous blocking socket is NOT what you should do with ICS which is asynchronous, non-blocking and event driven. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
