Fair enough, I suppose the best way to handle this is to track whether workers are working and pop up a message on onbeforeunload?
Cheers Chris On Nov 3, 9:04 am, Chris Prince <[EMAIL PROTECTED]> wrote: > Yes, workers stop executing when the browser is closed. Workers do > not have any opportunity to run "last-chance" code. > > The reasons for this are: > * Users generally don't like their actions to be delayed, especially > when they try to close a program. > * Even if workers could run some final code: > (a) it's unclear how many milliseconds longer the workers > should be allowed to run, and > (b) no matter how many milliseconds were chosen, worker > code could not rely on any particular actions completing, > because the amount of work you can do in N msec will > vary widely between machines. > > > > On Fri, Oct 31, 2008 at 4:45 PM, Travis <[EMAIL PROTECTED]> wrote: > > > I was wondering if a worker process stops when the browser closes > > regardless of whether its completed or not? > > > I am trying to implement a background process that runs a long running > > PHP file via the XMLHttpRequest module and I would like to store its > > return data in the Gears database.- Hide quoted text - > > - Show quoted text -
