[Bug 25251] Transaction ordering for readonly transactions

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25251

--- Comment #1 from Jonas Sicking <jonas@sicking.cc> ---
I suggest replacing the paragraph starting with "If multiple "readwrite"
transactions are attempting..." with the following:

Any transaction _created_ after a "readwrite" transaction MUST see the changes
written by the "readwrite" transaction. So if a "readwrite" transaction, A, is
created, and later another transaction B, is created, and the two transactions
have overlapping scopes, then B MUST see any changes made to any object stores
that are part of that overlapping scope. Due to the requirements in the
previous paragraph, this also means that the B transaction does not have access
to any object stores in that overlapping scope until the A transaction is
_finished_.

And then change the note to:

Generally speaking, the above requirements mean that any transaction which has
an overlapping scope with a "readwrite" transaction and which was created after
that "readwrite" transaction, can't run in parallel with that "readwrite"
transaction.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 14 November 2014 00:07:15 UTC