Hi,
I am working on an application that allows users to run database queries from a web browser (we are currently using Tomcat 5.0.25). A problem arises when a user starts a new query and then decides that they want to cancel it by hitting the browser "stop" button. After a lot of reading on this already, I appreciate that it is not possible for Tomcat to be notified that this has occurred, since no event is generated by the browser that Tomcat can detect. The solution I attempted was to start a background "pinger" thread in Tomcat which periodically writes back to the browser as the query is running. The theory was that if the user hits the "stop" button then I would get an IOException since the socket connection has been broken. In practice this does not happen, the pinger thread continues to write output without any exception or error occurring, and it is as if this output is being lost in a black hole somewhere! (the browser does not receive any more output after the stop button has been pressed, as expected).
Has anybody got any suggestions as to how I can get this to work, or a more general approach to solving the "stop" button problem?
Many Thanks! Les.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
