Then that write is when you will get the exception. Non-realtime tasks require special consideration when accessed in a browser. You should instead kick off the process and redirect the user to a page which polls the process status and has a nice bright red stop button which can signal the server to cancel the operation by interrupting the worker thread.
-----Original Message----- From: LeVan,Ralph [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 12:19 PM To: '[EMAIL PROTECTED]' Subject: RE: Detecting that a servlet should stop An IO error where? The message has already been read and the next IO I do is at write time when I'm all done. That's a little late in the process. Ralph > -----Original Message----- > From: Mike Perham [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 11:44 AM > To: [EMAIL PROTECTED] > Subject: RE: Detecting that a servlet should stop > > > You can't tell for sure. You will get an IOException but that can be > caused by a number of things. > > -----Original Message----- > From: LeVan,Ralph [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 10:37 AM > To: '[EMAIL PROTECTED]' > Subject: Detecting that a servlet should stop > > > How do I tell in my servlet that the user hit the stop button on their > browser? >
