W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2008

[whatwg] SQL storage and onunload

From: Brady Eidson <beidson@apple.com>
Date: Fri, 8 Feb 2008 09:24:58 -0800
Message-ID: <43364927-9FE5-410C-AF19-54348ACB3FCC@apple.com>
Though it would be very nice to have defined semantics wrt the unload  
handler, I always thought this work could be done with the  
beforeonunload handler, instead.

As far as the unload handler question, what are the semantics for  
XHR?  Seems the application of "saving some application state via I/O"  
is the same concept here, so the same rules should apply.


On Feb 8, 2008, at 1:44 AM, Alexey Proskuryakov wrote:

>  It seems to be a natural idea to save Web application state from an  
> unload event handler. But is it guaranteed that client-side database  
> API is still functional at this point? And if it is - can one queue  
> up more statements and/or transactions from statement callbacks?
>  There needs to be some limits put on this, as otherwise a script  
> could continue to use resources indefinitely after a browser window  
> is closed. But I do not see where it is specified, explicitly or  
> implicitly.
> - WBR, Alexey Proskuryakov
Received on Friday, 8 February 2008 09:24:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:39 UTC