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

Re: [chromium-html5] LocalStorage inside Worker

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 11 Jan 2011 14:37:16 -0800
Message-ID: <AANLkTi==68j0aF8qWku-zY2wHT1QkH0fFXYap6f-kXrE@mail.gmail.com>
To: Keean Schupke <keean@fry-it.com>
Cc: Jeremy Orlow <jorlow@chromium.org>, robert@ocallahan.org, Glenn Maynard <glenn@zewt.org>, Charles Pritchard <chuck@jumis.com>, public-webapps WG <public-webapps@w3.org>
On Tue, Jan 11, 2011 at 2:11 PM, Keean Schupke <keean@fry-it.com> wrote:
> Would each 'name' storage have its own thread to improve parallelism?

Your vocabulary is a bit off since from an API point of view, storage
areas don't have threads, the execution environments in workers and
windows do.

But if your question is weather one worker can open the storage named
"foo", while another window or worker is holding the storage named
"bar" open, then the answer is yes.

> would:
> withNamedStorage('x', function(store) {...});
> make more sense from a naming point of view?

I have a different association for 'with', especially in context of
JavaScript, so I prefer 'get'. But others feel free to express an

/ Jonas
Received on Tuesday, 11 January 2011 22:38:08 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:29 UTC