- Original Message -
From: "Fastream Technologies" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 14, 2007 4:58 PM
Subject: Re: [twsocket] Bug in MT THttpConnection close logic
> Hello Arno,
>
> Thanks for your attention once again! I have
;Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 14, 2007 5:22 PM
Subject: Re: [twsocket] Bug in MT THttpConnection close logic
> One question, why don't you call THttpMTConnection.Close?
> TCustomWSocket.InternalClose calls Shu
One question, why don't you call THttpMTConnection.Close?
TCustomWSocket.InternalClose calls ShutDown(1) and subsequently
close the socket handle as well as triggers SessionClosed
as needed. So far I had no problems with calling Close given
all data has been sent before (that is calling it from eve
BTW, this does this also mean all ICS components need a timeout?
Regards,
Gorkem
- Original Message -
From: "Francois Piette" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 14, 2007 12:13 PM
Subject: Re: [twsocket] Bug in MT THttpConne
Thanks! Will let you know if the timeout mechanism will work.
BR,
SZ
- Original Message -
From: "Francois Piette" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 14, 2007 12:13 PM
Subject: Re: [twsocket] Bug in MT THttpConnection close
> For some reason sometimes with slow/WAN connections, when clients are
> remote, this code does not work and the client object is "hung",
eventually
> filling the maximum number of connections.
Calling Shutdown will initiate the TCP session shutdown, that is breaking
cleanly the connection. But i
