> Instead put blocking, lengthy tasks like executing a SQL > into worker threads and send the result when thread has finished > the job.
ADO also supports non-blocking SQL Server commands, with an event triggered when the command finishes, so you don't even need threads for SQL. ADO uses a thread internally, but that's a Microsoft problem, not ours. My ComCap application handles dozens of sockets simultaneously, as well as updating several different SQL databases, all in a single thread. Angus -- 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
