> Abort() IMHO. Is this correct? No, since receiving this notification from winsock does not necessarily mean that all data has been received on the application level.
-- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html Fastream Technologies wrote: > Hello, > > I mean the FD_CLOSE() is called when a close is detected right. > However, the last two lines calling Close() should be changed with > Abort() IMHO. Is this correct? > > Thanks, > > SZ > > ----- Original Message ----- > From: "Fastream Technologies" <[EMAIL PROTECTED]> > To: "ICS support mailing" <firstname.lastname@example.org> > Sent: Wednesday, July 25, 2007 12:03 AM > Subject: Is this a bug or a missing feature in wsocket.pas? > > >> Hello, >> >> In the description of winsock error 10053 which I get with my proxy, >> I read: >> >> "TCP/IP scenario: A connection will timeout if the local system >> doesn't receive an (ACK)nowledgement for data sent. It would also >> timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN >> is ACK'd, it will eventually timeout if a FIN is not returned)." >> >> Is the case in the last sentence addressed by ICS? I mean, what to >> do to sockets in CLOSE_WAIT state? I normally destruct my >> thttpconnection instance (or send to pool) in a Postthreadmessage >> posted in OnSessionClosed. Is there a better way to do it? >> >> Best Regards, >> >> SZ -- 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