On Nov 29, 2007, at 14:20, Arno Garrels wrote:

> Hard to tell, a good compromise is using TWSocketServer given
> any lengthy task is run in worker threads. I think separating
> socket IO work from other tasks by using worker threads for those
> tasks considered "lengthy" is the way to go. The definition of
> "lengthy" however is another story then. <g>

The problem I have is that most of the processing is atomical to the 
client transaction, that is,

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

Reply via email to