I would say without affecting what resulting data is stored in the database.
This since the order the events fire in can affect the state of the javascript
environment kept by the web page.
/ Jonas
Made the change in the speclet:
There is no guarantee about the order that results from
On Thu, Apr 21, 2011 at 4:37 PM, Eliot Graff eliot.gr...@microsoft.com wrote:
What we're trying to convey is that two requests placed against different can
execute in any order, but that this doesn't matter, and the isolation mode
and the transaction scheduling ensures that.
Thanks, that
On Thu, Apr 21, 2011 at 2:51 PM, Eliot Graff eliot.gr...@microsoft.com wrote:
In the changeset I commited on 20 April, I had this change for the last
sentence of step 4 of the description of the lifetime of a transaction in
section 3.1.7: [1]
Previous:
Similarly, the isolation mode ensure
What we're trying to convey is that two requests placed against different can
execute in any order, but that this doesn't matter, and the isolation mode
and the transaction scheduling ensures that.
Thanks, that makes sense. Any objection to using your phraseology?
There is no guarantee
