W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [IndexedDB] Transaction Auto-Commit

From: David Grogan <dgrogan@chromium.org>
Date: Fri, 19 Aug 2011 18:10:02 -0700
Message-ID: <CAOZbSt3OErTPqvyo0aFfA8O4d31O_rVLTFXPCzfMWgosXshHmg@mail.gmail.com>
To: Israel Hilerio <israelh@microsoft.com>
Cc: "joran@ronomon.com" <joran@ronomon.com>, "Jonas Sicking (jonas@sicking.cc)" <jonas@sicking.cc>, "public-webapps@w3.org" <public-webapps@w3.org>
On Tue, Aug 16, 2011 at 10:52 AM, Israel Hilerio <israelh@microsoft.com>wrote:

> On Thursday, August 04, 2011 11:02 AM, Jonas Sicking wrote:
> [snip]

>  > I'd be open to allowing read transactions which are started after a
> write transaction to see the before-write database contents. Would
> definitely want input from Microsoft and Google first though. There is also
> a question if this should be opt-in or default behavior.
> > My gut feeling is to leave this for version 2. Though that of course
> removes the ability to make it default behaviour.
> Microsoft would like to push this change to v2 and try to get the v1 spec
> to Last Call soon so we can start getting some adoption on this technology.

If this change were incorporated into the spec, our current implementations
would still conform, correct?  Allowing read transactions to start before a
read_write transaction is finished seems to give browsers the choice of
implementing an optimization without invalidating current behavior.

That said, we (chromium) wouldn't implement such an optimization for quite a
while, so when it goes into the spec is not of much practical importance.
Received on Saturday, 20 August 2011 01:10:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:23 UTC