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

Re: [Bug 10400] New: [IndexedDB] IDBCursor.continue should return an IDBRequest

From: Jeremy Orlow <jorlow@chromium.org>
Date: Thu, 19 Aug 2010 21:34:27 +0100
Message-ID: <AANLkTinKA_GMxP5kU43uJ0r_YND2th7XOQmycJimEyW0@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: public-webapps@w3.org
On Thu, Aug 19, 2010 at 7:06 PM, Jonas Sicking <jonas@sicking.cc> wrote:

> Hi All,
> Ben Turner put some comments in the bug, but I'll add a bit here too.
> The idea was that cursor.continue() should reuse the same request that
> was created when .openCursor was called. That makes using cursors
> significantly easier since you just have to register one 'success'
> handler, instead of registering a new one for each call to
> .continue().

Yes, after Ben mentioned it, I vaguely remembered us talking about this a
while back.  :-)

> We also remove the return value from .continue() and make it "return
> void". It doesn't make sense to return a bool indicating if this was
> the last entry or not since we only know that information
> asynchronously.

Do you have thoughts on whether it should return an IDBRequest object
though?  Obviously the request object it returns would be the same one
originally returned from .openCursor().  As I mentioned in my reply, I could
see it being confusing, but for completeness I wanted to hear your thoughts.

Received on Thursday, 19 August 2010 20:35:16 UTC

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