> To clarify what Francois said, you could have a thread that does that > processing, and posts messages back to your main form with the data, which > then calls WSocket.Send to send that data. Then you don't have to worry > about multithreaded sockets.
This result in a better programming model where "task" are clearly separated. A task is processing data to produce some output. Another task is to tranmit the output. And I would say a third task is to have a user interface. -- 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
