Put a heartbeat on the client - Use either an applet or a form with a
timeout before it resubmits. If you don't get the heartbeat at the server,
than terminate the background thread. (This assumes that the initiat
processing can be put in a background thread.)
-----Original Message-----
From: Reiche, Mike [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 3:53 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Detect Browser "Disconnect"
WebLogic (sometimes) throws exceptions when you write to the response socket
(out.println) after a user has clicked on the 'stop' button or the browser
has timed out. Tomcat may do the same.
Mike
>-----Original Message-----
>From: Devon Ziegler [mailto:[EMAIL PROTECTED]]
>Sent: Monday, April 30, 2001 11:58 AM
>To: [EMAIL PROTECTED]
>Subject: Detect Browser "Disconnect"
>
>
>Well, I waited a while and decided to ask this question again
>(WITHOUT read
>receipts this time!!! :) (what a waste of email bandwidth)).
>Is there any
>way to determine if the browser that requested a page is still
>waiting for
>the response? I would like to terminate lengthy queries and
>computations if
>the browser asking for the page is no longer waiting for it.
>We're using
>Linux 6.2 with tomcat 3.2.1 standalone and using Servlets.
>Any thoughts?
>Is this impossible? Anybody? Anybody?
>
>---
>Devon C. Ziegler
>[EMAIL PROTECTED]
>[EMAIL PROTECTED]
>Cell: (678) 485-7025
>Office: (678) 589-4126
>
