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

[whatwg] localStorage + worker processes

From: Michael Nordman <michaeln@google.com>
Date: Fri, 20 Mar 2009 15:42:01 -0700
Message-ID: <fa2eab050903201542o6cc2a822o34f7a5af5566ddf6@mail.gmail.com>
On Fri, Mar 20, 2009 at 3:34 PM, Dmitry Titov <dimich at google.com> wrote:
> On Fri, Mar 20, 2009 at 2:39 PM, Drew Wilson <atwilson at google.com> wrote:
>>
>> One alternative I'd like to propose is to remove access to localStorage
>> for dedicated workers, and give SharedWorkers access to localStorage, but
>> have that storage be partitioned by the worker name (i.e. the worker can
>> access it, but it's not shared with web pages or any other workers and so
>> you don't have any synchronicity issues).
>
> This may be interesting. It allows to keep single API for localStorage. Most
> of the usage is probably going to happen inside such a worker - in other
> words, sharing the info with other pages of the same origin may not be
> needed, and there is always async communication when a live page wants to
> share data with a shared worker.

Interesting... essentially a page/worker specific persistent
repository... doesn't span in the way "localStorage" does.
Received on Friday, 20 March 2009 15:42:01 GMT

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