W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2007

[whatwg] Asynchronous database API feedback

From: Krzysztof Żelechowski <giecrilj@stegny.2a.pl>
Date: Tue, 11 Dec 2007 18:03:55 +0100
Message-ID: <1197392635.6515.65.camel@a1dmin.vola.spe.com.pl>

Dnia 10-12-2007, Pn o godzinie 16:04 -0800, Dan Mosedale pisze:
> On Dec 10, 2007, at 12:21 PM, Geoffrey Garen wrote:
> >>> I'd hate for GMail to mysteriously stop working every couple of  
> >>> days just because of some background process that I had no  
> >>> knowledge of. As a developer, how would you debug such a problem?  
> >>> As a tech support worker, how would you explain it to an end user?
> +1.  Having a bug in a single web-app be able to completely freeze the  
> entire UI of the entire browser (not just that window/tab) seems like  
> a pretty painful user experience, almost to the point of being  
> unacceptable.  If an end user ran into this problem very often, I  
> would expect them to blame the browser, and perhaps even switch to a  
> browser which didn't have this problem (i.e. didn't support  
> localStorage).
> As a user, assuming a synchronous interface with timeouts, I would  
> almost certainly want my browser to enforce a _much_ shorter timeout  
> than 5 seconds... something on the order of 200ms, maybe.  Anything  
> that makes repainting stop just feels really bad.

Does that mean asynchronous script execution as well?  Because if not,
it cannot be done, except that the browser implements a script kill
timeout, which applies to all scripts, including local database access
when it is supported.

Best regards,
Received on Tuesday, 11 December 2007 09:03:55 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:59 UTC