W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

Re: [Bug 10430] New: [IndexedDB] We need to make it more clear IDBRequests can be reused and spec readyState's behavior

From: Jeremy Orlow <jorlow@chromium.org>
Date: Mon, 1 Nov 2010 09:49:55 +0000
Message-ID: <AANLkTinuD4WGbx+B1_MtcJNLOASMs-itp6nK9miatouX@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: bugzilla@jessica.w3.org, public-webapps@w3.org
On Mon, Nov 1, 2010 at 9:42 AM, Jonas Sicking <jonas@sicking.cc> wrote:

> On Mon, Nov 1, 2010 at 1:46 AM, Jeremy Orlow <jorlow@chromium.org> wrote:
> > Actually, what's the use case for readyState?  I can't think of any uses
> > that we'd want to encourage.  Maybe we should just remove it.
> The use-case that I've heard in similar situations goes something like
> this:
> Code makes a request and at some point later hands the request to some
> other piece of code which is interested in the result.
> The other piece of code doesn't necessarily know if a result has been
> returned yet or not. Using readyState it can either simply get
> .result, or it can add a event listener for the "success" event and
> wait for the event to fire.
> I think that makes sense here too.

What about the cursor case though?  Given that we're re-using the same
request object, I really don't think it makes much sense.

Received on Monday, 1 November 2010 09:50:46 UTC

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