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

Benjamin Smedberg benjamin at smedbergs.us
Thu Sep 3 13:43:59 PDT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/3/09 4:24 PM, Drew Wilson wrote:
> I think the canonical racy case is "the page wants to keep a counter for
> the number of times event X occurs" in a cookie or local storage.

Is it important that continue to work without racing? I don't think it's
especially important: it's similar to how HTTP responses may race. The only
thing I'm particularly concerned about is data consistency so that setting
document.cookie does not inadvertently undo changes which happened while the
script was executing.

- --BDS


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFKoCqPSSwGp5sTYNkRAm7YAJ9TtPVdK8j6sOwRD6ZA+qn45sU0BACfSPlZ
vZMlhKARLnu9PU57C3xjrP4=
=0kXs
-----END PGP SIGNATURE-----



More information about the whatwg mailing list