[whatwg] Storage mutex feedback

Jonas Sicking jonas at sicking.cc
Sun Aug 30 21:12:26 PDT 2009

On Sat, Aug 29, 2009 at 10:06 PM, Ian Hickson<ian at hixie.ch> wrote:
> On Fri, 28 Aug 2009, Kevin Benson wrote:
>> How about:
>> commitStorageUpdates
>> ... since a new transactor cannot write to storage until a commit point
>> is reached by the current transactor finishing up and releasing the
>> lock.
> That could work too.
> Upon further consideration I've renamed getStorageUpdates() to
> yieldForStorageUpdates().

'yield' usually refers to halting execution. I would expect the above
name to stop the current thread and allow other threads to run. While
that is what could be happening here, I'm not sure that is the primary
function of the call.

I really liked Darin's (?) suggestion of allowStorageUpdates as that
seems to exactly describe the intended use of the function. We no
longer prevent other page from updating the storage.

/ Jonas

More information about the whatwg mailing list