[whatwg] localStorage mutex - a solution?

Robert O'Callahan robert at ocallahan.org
Sun Nov 8 17:33:27 PST 2009

On Mon, Nov 9, 2009 at 1:42 PM, Adam Barth <whatwg at adambarth.com> wrote:

> As I mentioned to Ian at TPAC, one way to make this more predictable
> is to release the lock on *every* function call and return.  This
> provides content enough atomicity to build whatever locks it needs.

Then simple refactorings that should be semantics-preserving --- like
extracting a block of code into a shared function --- would break atomicity.
This also places a new burden on JS implementations.

"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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091109/d03bd038/attachment-0002.htm>

More information about the whatwg mailing list