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

Re: [IndexedDB] Callback order

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 18 Jun 2010 19:24:08 -0700
Message-ID: <AANLkTin-FsQ38PgPlDSfl5b8lfIGmnGxWDuCe0Zxjl-E@mail.gmail.com>
To: Jeremy Orlow <jorlow@chromium.org>
Cc: Webapps WG <public-webapps@w3.org>
On Fri, Jun 18, 2010 at 7:01 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
> I think determinism is most important for the reasons you cited.  I think
> advanced, performance concerned apps could deal with either semantics you
> mentioned, so the key would be to pick whatever is best for the normal case.
>  I'm leaning towards thinking firing in order is the best way to go because
> it's the most intuitive/easiest to understand, but I don't feel strongly
> about anything other than being deterministic.

I definitely agree that firing in request order is the simplest, both
from an implementation and usage point of view. However my concern is
that we'd lose most of the performance benefits that cursors provide
if we use that solution.

What do you mean with "apps could deal with either semantics"? You
mean that they could deal with the cursor case by simply being slower,
or do you mean that they could work around the performance hit
somehow?

/ Jonas
Received on Saturday, 19 June 2010 02:25:01 GMT

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