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

Re: [chromium-html5] LocalStorage inside Worker

From: Keean Schupke <keean@fry-it.com>
Date: Tue, 11 Jan 2011 09:04:44 +0000
Message-ID: <AANLkTind=U6BkrKOu0W01PtVU6EN2fk3q_kNzA-XdRwh@mail.gmail.com>
To: Felix Halim <felix.halim@gmail.com>
Cc: Glenn Maynard <glenn@zewt.org>, robert@ocallahan.org, Charles Pritchard <chuck@jumis.com>, Jonas Sicking <jonas@sicking.cc>, public-webapps WG <public-webapps@w3.org>
I think the idea is that JavaScript should not do unexpected things. The
suggestion to only make local storage accessible from inside callbacks seems
the best suggestion so far.


On 11 January 2011 06:20, Felix Halim <felix.halim@gmail.com> wrote:

> On Tue, Jan 11, 2011 at 1:02 PM, Glenn Maynard <glenn@zewt.org> wrote:
> >> localStorage should focus on simplicity and performance and ignore
> >> thread safety since, IMHO, localStorage is used for UI purposes or
> >> preferences settings (not data itself). If you open two tab, you
> >> change settings in one tab, you can just refresh the other tab and I
> >> believe both of them will have the same UI state again.
> >
> > It's used for data storage, too, particularly since it's widely
> > available in production; IndexedDB is not.
> Then, why don't introduce a new storage, like localStorageNTS (NTS =
> non thread safe), and allow this storage to be used everywhere...
> Felix Halim
Received on Tuesday, 11 January 2011 09:05:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:15 UTC