The servlet has no way of knowing that you hit stop, so it will keep on grinding. As far as I know, stop only closes all connections that the browser has opened in trying to build the page display. The servlet will only detect this when it trys to write to the response output stream and hits an IOException. Therefore, your servlet should flush() the output buffer after every write, in order to detect the closed connection as soon as possible. Bill
Does not a flush of the buffer commit the response and prevent any further info from being written?
Author and all-around good cowpoke
Joined: Mar 22, 2000
Executing flush "commits" the response headers, so you can't change them but the connection stays open. If you have a time consuming response generation process, doing some output and calling flush can show your user that some progress is being made.