And if the client is on the other side of a caching proxy there's still another layer of buffering between you writing to the socket and an error being returned.
On 30/03/2004, at 12:05 PM, Dossy wrote:
On 2004.03.29, Bas Scheffers <[EMAIL PROTECTED]> wrote:
Is it possible to detect the browser has close the connection?
Write to the socket. If the peer has closed the connection, you should get a SIGPIPE or somesuch.
Of course, the client can disappear *without* closing the connection (dial-up disconnect abruptly) ... but eventually (after 2MSL or whatever you have your kernel tuned to) the system will time-out the socket and it'll appear disconnected.
Does AOLserver bubble up the error writing to the socket back to the thread doing the writing (preferably as a Tcl error that can be catch'ed -- er, caught)? That'd probably be really annoying, now that I think about it, in the normal case.
-- Dossy
-- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
