Fastream Technologies wrote:
> Do I need to call shutdown on an errenous socket?
Not needed. 10054 Connection reset by peer doesn't mean
an error, the peer simply hung up the line.
> I think you did not
> read what I wrote carefully. I have connections objects hanging on a
> modified MT HTTP server.
As you wrote, OnClientClose will be called immediately, so cleanup
can be done from there, or am I missing something?
Arno Garrels [TeamICS]
> ----- Original Message -----
> From: "Wilfried Mestdagh" <[EMAIL PROTECTED]>
> To: "ICS support mailing" <firstname.lastname@example.org>
> Sent: Friday, March 09, 2007 3:50 PM
> Subject: Re: [twsocket] Problem with web server socket closing
> aftererroneous send
>> Hello Fastream,
>> You should do nothing. It is the task of the client to reconnect if
>> session is broken.
>> Rgds, Wilfried [TeamICS]
>> Friday, March 9, 2007, 11:10, Fastream Technologies wrote:
>>> I have the following scenario:
>>> 1) Send() called
>>> 2) 10054 returned
>>> 3) Immediately by ICS OnClientClosed called
>>> 4) I detect the error in socket
>>> What should I do now? Should I call shutdown? Will the onclosed be
>>> called again if I do so? Which event will it call if not?
>>> Meanwhile, when errors occur, sockets stay hung! BTW, ICS web
>>> server code does not handle socket errors!!
>> 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