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

[whatwg] RFC: Alternatives to storage mutex for cookies and localStorage

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 5 Sep 2009 22:49:06 +1200
Message-ID: <11e306600909050349tdaec1f1m19e62c50690627b9@mail.gmail.com>
On Sat, Sep 5, 2009 at 10:22 AM, Chris Jones <cjones at mozilla.com> wrote:

> And if the intention is to make scripts appear to run atomically, then I
> think there are better ways to specify that than storage mutex.
>

That sounds good, how?

My problem with storage mutex boils down to the fact that by the letter of
> the spec, a script can lock out the UA indefinitely by just reading a
> cookie.


What do you mean "lock out the UA"?


> Transactional semantics seems to be a better abstraction, and an ancillary
> benefit is that it's much easier to implement to boot.  Though even if it
> were harder to implement, I would still argue for it.
>
>
I agree with you. However, there is still the compatibility issue. (Some
people may also argue that what we currently have is simpler for authors
than any explicit transactional API --- personally I'm unsure if that
matters.)

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090905/834d52c2/attachment.htm>
Received on Saturday, 5 September 2009 03:49:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:52 UTC