> Imagine a server with many concurrent connections but that only allows one > connection at a time to submit a request, access/manipulate data and then > send the results back to all other connections. In other words all requests > (regardless of which connection it's coming from) must be serialized.
This is very easy to do with ICS :-) > Is the proper architecture to have one thread contain all the connections > and then, when an socket event fires, assign the request to a worker thread > (from a pool) which in turn attempts to access a critical section of another > thread (the data manipulation thread)? Not at all. Simply use a TWSocketServer in the main thread and no worker thread at all. All requests will be automatically serialized provided you never call the message pump and process the requests in one blocking function call. Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) 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
