W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2009

[whatwg] localStorage + worker processes

From: Aaron Boodman <aa@google.com>
Date: Sun, 22 Mar 2009 11:53:03 -0700
Message-ID: <278fd46c0903221153n16e0077bsba34ab49c4a8b93c@mail.gmail.com>
On Sun, Mar 22, 2009 at 11:21 AM, Drew Wilson <atwilson at google.com> wrote:
> I've thought about this more, and I'm afraid that if you start making the
> API cumbersome (forcing only async access) then apps are just going to use
> document.cookies instead of localStorage. I'd hate to see us radically
> change the API to support the worker case - I'd rather get rid of
> localStorage support from workers, or else just enforce a max time that a
> worker can hold the lock.

I don't believe that. Adding one async callback is no inconvenience
compared to the sad farce that is the document.cookie "API". Also,
localstorage has many benefits including structured storage and not
getting sent to the server in every request.

- a
Received on Sunday, 22 March 2009 11:53:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:47:49 GMT