Angus Robertson - Magenta Systems Ltd wrote: >> Looks like you try to workaround the asynchronous nature of TWSocket >> which were a bad idea. Where do you call this and what do you want >> to achieve? > > Waiting for all sockets to close cleanly may be necessary before > terminating an application, to ensure continuously streamed data is > not lost.
I do not see a reason why one must wait in a loop processing messages with calls to sleep()in order to achieve that, that's often a hint to bad design and should be avoided. -- 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