Hello Wilfried, Ok, I will make that way, but do you know the implications of doing the way I said? It can cause the host to make some half-closed connections?
Éric ----- Original Message ----- From: "Wilfried Mestdagh" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Wednesday, April 02, 2008 3:21 AM Subject: Re: [twsocket] Connecting and Disconnecting Hello Éric, When it is disconnected then OnSessionClose is fired. There you post a message to a custom message handler where you connect again. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Tuesday, April 1, 2008, 22:15, Éric Fleming Bonilha wrote: > Hello > What is the implication on the TCP control of disconnecting and > connecting using the same TWSocket object? what I mean is that: > FSocket.Disconnect; > FSocket.Addr := 'x.x.x.x'; > FSocket.Port := '80'; > FSocket.Connect; > What is the implication of doing that on sequence?? > I ask that because we are having some problems with the server > machines (Server is not ICS), apparently it keeps the connection on > it´s memory and after a lot of connections and disconnections it stop > working (The host device) because it has a lot of "half-closed" > connections. > This is the right way of reconnecting? If not, what should be the > best? Try to reconnect on the OnSessionClosed? > Thanks! > Éric -- 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 -- 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
