Hello Mitchell, Yes there should be a Connect (or Listen) before sending something. UDP is not session related but it is the way TWSocket is written. But for UDP you dont have to wait for an event, you can call Connect and in next line of code you can call SendStr. Also it is OK to Release the TWSocket when you have received the answer.
But what I don't understeand is where is the handle lost ? --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Monday, October 1, 2007, 18:34, Mallough, Mitchell W HS wrote: > 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 -- 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
