Unfortunately, I don't think there's currently any way to detect this. Ordinarily, all output is buffered and sent at once at the end of the transaction. If you call self.response().flush(), it will attempt to immediately send all response that has been generated up to that point. That would be a logical place for WebKit to try to detect the closed client socket and perhaps raise an exception to end the response. But I'm pretty sure it doesn't in fact raise this exception; instead, it just silently throws away the rest of the response. You could try testing this; I might be wrong...
If you feel like trying to fix this, it might not be all that hard but will definitely require mucking around in the WebKit internals. - Geoff > -----Original Message----- > From: Brett Funderburg [mailto:[EMAIL PROTECTED]] > Sent: Monday, August 26, 2002 5:33 PM > To: [EMAIL PROTECTED] > Subject: [Webware-discuss] detecting if client is still around > > > Say, for example, a browser client requests a servlet that > performs some > lengthy operation. What is the correct way to determine if the client > socket is still open to allow the servlet to decide if it > should abort the > operation or continue processing? > > Thanks, > > brett > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss > ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
