W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: [IndexedDB] Isolation mode -- edit

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 21 Apr 2011 16:28:11 -0700
Message-ID: <BANLkTikf-Az-TXqHpYXNH6HutVsvB9b+5g@mail.gmail.com>
To: Eliot Graff <Eliot.Graff@microsoft.com>
Cc: public-webapps <public-webapps@w3.org>
On Thu, Apr 21, 2011 at 2:51 PM, Eliot Graff <Eliot.Graff@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 that it doesn't matter which order requests placed against different transactions are executed.
>
> Changed To:
> Similarly, the transaction mode ensures that the order of requests placed against different transactions has no effect with respect to execution order.
>
> The concept we're trying to convey is not clear to me. Pablo thought that it might be better to simply remove the entire sentence, but he asked that I check with the group. Does anyone have any concern that removing that sentence would omit some important information?

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.

I think it's worth having this spelled out in the spec.

/ Jonas
Received on Thursday, 21 April 2011 23:29:07 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:44 GMT