This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8358 - [WA] Fix for the localStorage mutex problem - release for *any* API operation except localStorage itself
Summary: [WA] Fix for the localStorage mutex problem - release for *any* API operation...
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Web Storage (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-23 23:09 UTC by Rob Ennals
Modified: 2009-11-25 23:54 UTC (History)
3 users (show)

See Also:

Attachments

Description Rob Ennals 2009-11-23 23:09:49 UTC 
This is a proposal I made earlier on the whatwg mailing list, and then presented at TPAC. I believe I said I would file a proper bug report for it.


How about this for a solution for the localStorage mutex problem:

"the user agent MAY release the storage mutex on *any* API operation except localStorage itself"

This guarantees that the common case of "several storage operations in a row with nothing in-between" works, but gives the implementors the freedom to release the storage mutex wherever else they find they need to.

I ran this by a few people at the W3C tpac (where I am now) and everyone I talked to seemed to think this would work.


-Rob
Comment 1 Ian 'Hixie' Hickson 2009-11-25 23:54:13 UTC 
Implementors on the WHATWG list didn't seem happy with this unfortunately.