Stefan Paege wrote: > Francois Piette schrieb: >> I can't answer precisely to your question. I should have a look at >> the source code to see where the critical sections are placed. >> I never do this kind of programming. I organize inter-thread >> communication using messages. Never share any component between two >> threads. It is much much safer. I separate the tasks into black >> boxes communicating thru simple messages. > > Arno. perhaps you can jump in and offer some more info? > Is there any example besides the ThrdServV3 project (which does not > include what I'm after)?
I also haven't had a look at that unit for quite a long time. It was made to derive a SSL capable, multi-threading server for testing thread safety of the ICS-SSL extension. Most of the events are executed in worker thread context, you can display current ThreadID thru GetCurrentThreadID() in order to know in which thread your are. Are you really sure that you need multi-threading at all? TWSocketServer can handle hundreds of clients w/o any problem in a single thread, makes life much easier ;-) > > TIA > > -- > > > Elektronik-Labor Carls GmbH & Co. KG > > Stefan Paege > > Fon: +49 5973 9497-23 > Fax: +49 5973 9497-19 -- 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
