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: Sat, 8 Jan 2011 11:10:44 +0000
Message-ID: <AANLkTimvx3bZB2QKUJA8wK44_CqxDDruOJPXSUZF=fd7@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Charles Pritchard <chuck@jumis.com>, Jonas Sicking <jonas@sicking.cc>, public-webapps WG <public-webapps@w3.org>
On 8 January 2011 10:00, Glenn Maynard <glenn@zewt.org> wrote:

> On Sat, Jan 8, 2011 at 4:06 AM, Keean Schupke <keean@fry-it.com> wrote:
> > If access had to be from inside an "atomic" block (a callback from a
> single
> > storage-thread) then this would fix access from multiple tabs/windows as
> > well as from worker threads.
>
> Your suggestion and Jonas's are very similar.  I think the difference
> is that you're suggesting an API that would permit non-serialized
> access to the objects, by using transactional methods, where Jonas's
> completely serializes access.  Jonas's is much simpler; I don't think
> the complexity of this type of transactional access is needed, or
> appropriate for simple Storage objects.
>
> --
> Glenn Maynard
>

I am suggesting that as the semantics are the same, People can think of this
like serialised access, but implementers can use STMs to make their browser
faster than the competition (if they want). To the user it will look the
same.

Cheers,
Keean.
Received on Saturday, 8 January 2011 11:11:16 GMT

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