Kurt Andersen wrote: > I have now implemented a working multithreaded test (server) > application which uses both the TWSocket and the TSslWSocket in a > non-blocking manner.
Just a side note to your design "One Thread Per TWSocket Instance", it's not optimal IMO. TWSocket objects allocate at least one shared, hidden window per thread which is waste of resources and decreases the maximum possible number of concurrent client connections. TWSocket actually works non-blocking it uses the non-blocking winsock API. What is blocking the socket I/O is lengthy tasks running in the same thread context. > I just have to be sure that I understood your reference to > f_ERR_remove_state(unsigned ThreadID). > Should I call this function just before the Thread's execute method > returns, sending the threads ThreadID as param ? Yes, it is a cleanup function. -- Arno Garrels -- 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
