Hello, I have read the description and believe that this could be useful with socket-pooling (like thread pooling). As you said, for this technique, we need the shutdown/close not to destroy the twsocket. It seems the paradigm changes a bit but in the code level I doubt it would require too much effort.
Best Regards, SubZero ----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Saturday, July 29, 2006 5:30 PM Subject: [twsocket] AcceptEx() in a MT socket server > Hello, > > Today I found AcceptEx() in winsock API > (http://msdn.microsoft.com/library/en-us/winsock/winsock/acceptex_2.asp?frame=true) > and I wonder whether the function might be usefull in a > multi-threaded TWSocketServer. It is capable to accept into an > already existing socket which promises to be very fast when > plenty of connections need to be accepted. Is it possible to > assign the sAcceptSocket to property TWSocket.Handle? And how > can I achieve that calling TWSocket.Close wont close the > socket handle so it can be reused? > > --- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > > > > -- > 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 -- 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
