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

[whatwg] localStorage mutex - a solution?

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 24 Nov 2009 16:26:33 -0800
Message-ID: <63df84f0911241626n6f9e79ackb2eee381673f2089@mail.gmail.com>
On Tue, Nov 24, 2009 at 3:12 PM, Rob Ennals <rob.ennals at gmail.com> wrote:
> Yes. I think that *any* DOM operation, including getElementById should
> be allowed to release the storage mutex. If we start specifying
> particular categories of API that do or do not release the mutex then
> thing will just get confusing, or we will find that we have missed
> something important.

"Allowed to release" or "must release"?

If it's "allowed to release" then that's not really helping that much
since in the end different implementations might still do different
things, causing incompatibilities.

If "must release" then I have no idea how to implement that. There are
hundreds of API entry points, and I really don't want to add code to
release the mutex in each and every one of them. Both for code sanity
reasons, and for performance reasons.

/ Jonas
Received on Tuesday, 24 November 2009 16:26:33 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:19 UTC