Of course, what's shipping in IE 8 is broken in that it doesn't support
run to completion (and neither will Chrome 4). So honestly I'm not super
compelled by the IE shipped argument.
I still think giving a close approximation to run to completion (repeatable
reads semantics) + a callback for
For those not following WhatWG: Ian just responded to the latest round of
localStorage feedback there and I just elaborated on my proposal.
On Wed, Dec 2, 2009 at 2:06 AM, Jeremy Orlow jor...@chromium.org wrote:
Of course, what's shipping in IE 8 is broken in that it doesn't support
run to
I haven't been following the localStorage mutex discussion in detail,
but have we already rejected the idea of having content specifically
ask for the mutex via a transaction callback, similar to how web
databases work?
localStorgage.atomicTransaction(function() {
localStorage[counter]++;
});
On Tue, Dec 1, 2009 at 6:18 PM, Adam Barth w...@adambarth.com wrote:
I haven't been following the localStorage mutex discussion in detail,
but have we already rejected the idea of having content specifically
ask for the mutex via a transaction callback, similar to how web
databases work?
On Tue, 1 Dec 2009, Adam Barth wrote:
I haven't been following the localStorage mutex discussion in detail,
but have we already rejected the idea of having content specifically ask
for the mutex via a transaction callback, similar to how web databases
work?
One of the limitations is we
