W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: IndexedDB, what were the issues? How do we stop it from happening again?

From: Tobie Langel <tobie@fb.com>
Date: Thu, 14 Mar 2013 22:47:55 +0100
To: Alex Russell <slightlyoff@google.com>
CC: Jarred Nicholls <jarred@webkit.org>, public-webapps WG <public-webapps@w3.org>
Message-ID: <1DE156203AA24D52A3DAEA7CEB9C63AD@fb.com>
On Thursday, March 14, 2013 at 7:54 PM, Alex Russell wrote:
> On Wednesday, March 6, 2013, Tobie Langel wrote:
> > Sync APIs are useful to do I/O inside of a Worker.
> 
> 
> I don't understand why that's true. Workers have a message-oriented API that's inherently async. They can get back to their caller "whenevs". What's the motivator for needing this?
There's no need per se. Sync API are easier to handle, and given you're already out of the UI thread, blocking in that context isn't much of an issue.
> > They're also critical for data consistency in some scenarios, e.g. updating the database after a successful xhr request when a worker is about to be terminated.
> 
> Unload-catching is a known bug in much o the web platform. Why would we enable it here?

Nevermind. The Web Worker termination process (now?) says scripts get aborted anyway.

--tobie
Received on Thursday, 14 March 2013 21:50:08 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT