Wilfried, I did a quick code audit yesterday, and found that Release is called in both SessionClosed and Disconnect. I am still fairly new to Winsock communications and ICS, but it seems as though this might be an issue with proper shutdown and destruction of the socket. The rapid open / close may not be a root cause.
What is a good resource for navigating the various methods and when they should be called? I noticed Destroy calls Close which calls InternalClose which calls Exit and Shutdown. When I say "calls" I understand some of these are message-based and therefore delayed. I noticed that Destroy also calls DeallocateSocketHwnd. My understanding of Release is that it posts a message which ultimately results in Destroy. Does it seem reasonable that the Release call in Disconnect should be changed to a Close or CloseDelayed, and the Release in SessionClosed remain? I will do some additional testing and further educating myself, but any input and guidance is appreciated. Thanks, ~Mitch -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilfried Mestdagh Sent: Monday, October 01, 2007 12:40 AM To: twsocket@elists.org Subject: Re: [twsocket] Lost handles using TWSocket. Hello Mitchell, Never have seen this problem, but I'm not fully understeand. You talk about rapid open / close, but you use UDP (wich is not session related)? Can you explain this again, maybe I have misunderstood. --- 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
