stop waiting?
But seriously.. if you're just using the browser to 'launch' an extremely long-running process, you could try spawning a new
Thread to do the long process, and use some sort of 'polling' to determine if the job is done. That is...
1) request the URL that launches the process.
2) after any 'setup work' (like authorization, connections, etc) launch a thread to do the processing.
3) forward to a
JSP page that uses HTML meta refresh tags to...
4) request a 'status' page. This page will query some area that will be used by the Thread you launched, to notify the user that the process is "done".
5) If not done, then reload the meta refresh page, else.. load a 'finished' page
The 'area' could be the Session, or a database, or a file.
[ February 25, 2004: Message edited by: Mike Curwen ]