The way the code stands now: Module Method Socket Activity ------------- --------------- Launch FSocket.Connect SessionConnected FSocket.SendStr ResponseReceived FSocket.Receive Destroy FSocket.Release (was FSocket.Free)
There are Disconnect & SessionClosed methods in the module which never get hit. I assume this is related to your comment that UDP is not session-based. If UDP is not session-based, then should there be a Connect at all? Perhaps the lost handles are related to there being a Connect operation on a socket that is UDP? Sorry if I am showing my lack of knowledge in this area, but your feedback is helping a great deal. Thanks, ~Mitch -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilfried Mestdagh Sent: Monday, October 01, 2007 8:12 AM To: ICS support mailing Subject: Re: [twsocket] Lost handles using TWSocket. Hello Mitchell, > Does it seem reasonable that the Release call in Disconnect should be > changed to a Close or CloseDelayed, and the Release in SessionClosed > remain? If you wants to destroy from within an event handler then call Release. Yes it indeed post a message to destroy it outside the event handler. You do not need to close it first. Same for CloseDelayed, it call Close in an event handler. But you use UDP so no need to Close as only TCP is session related. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz -- 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
