[whatwg] Storage mutex and cookies can lead to browser deadlock

To be clear, I'm not trying to reopen the topic of giving cookie access to
workers - I'm happy to restrict cookie access to document context (I
probably shouldn't have brought it up again).
I do agree with Jeremy that we should rethink the spec language around
cookie consistency to reflect what implementors are actually willing to


On Thu, Sep 3, 2009 at 6:17 PM, Jeremy Orlow <jorlow at chromium.org> wrote:

> On Fri, Sep 4, 2009 at 8:17 AM, Benjamin Smedberg <benjamin at smedbergs.us>wrote:
>> What kind of conflict? There is no need to "merge" individual cookies:
>> whichever one was set (or removed) last wins.
> I think this strategy would work fine for cookies since the HTTP side of
> them is inherently racy.  I think such behavior would be pretty
> counter-intuitive for localStorage, though.
> If we did go with this strategy, I think we could give access to shared
> workers, and someone could use those if they needed better "atomicity".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090903/076b73ee/attachment.htm>

Received on Thursday, 3 September 2009 18:25:09 UTC