This is less of a socket question and more of an implementation question. 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.
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)? Thanks for the input. -- 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
