W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [Bug 11348] New: [IndexedDB] Overhaul of the event model

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 27 Jan 2011 20:04:50 -0800
Message-ID: <AANLkTi=aXkLUAHapnw-5vWWcb=vdgrTwD+93hCMiC7tL@mail.gmail.com>
To: Jeremy Orlow <jorlow@chromium.org>
Cc: Axel Rauschmayer <axel@rauschma.de>, public-webapps@w3.org
On Thu, Jan 27, 2011 at 7:16 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
> On Thu, Jan 27, 2011 at 5:48 PM, Jonas Sicking <jonas@sicking.cc> wrote:
>>
>> On Thu, Jan 27, 2011 at 5:30 PM, Axel Rauschmayer <axel@rauschma.de>
>> wrote:
>> > I am really sorry to bring this up again, but: Why not separate
>> > concerns? Why not separate input data and output data?
>> >
>> > If onsuccess and onerror were handed in as an input parameters, would
>> > there be any need for readyState, LOADING, and DONE?
>>
>> We decided a long long time ago, based on input from web developers,
>> to use DOM-Events as notification mechanism. We went through the same
>> thing in the FileReader API where I initially suggested using a
>> different type of callback, but got the feedback that developers
>> preferred to use DOM-Events.
>>
>> Also note that the reason that your suggestion removes the need for
>> readyState is that your proposal decides to drop support for the
>> use-case that readyState aims to help solve. I.e. the ability to
>> register additional event handlers sometime after the request is
>> created.
>
> I'm still not convinced this use case is necessary either, but we've already
> argued that to death, so let's not start up again.
> Is all of this what was implemented in FF4b9?  If so, I'll do it in
> Chromium, though the event.target syntax really is kind of horrible.

Yup, this is all in FF4b (can't remember if it was in 9, but it is in
10 which is the latest released one).

> Lastly, let's say you're doing cursor.continue() on an index cursor, how can
> you get a handle to the objectStore?  I believe you can't.  Should we add in
> something for that?  (Most likely give the index a link to its object store?
>  And maybe even give a cursor a link back up as well?)

Yup, we added a .objectStore property on IDBIndex.

The call to .continue() returns a IDBRequest (same one as was
originally returned from .openCursor()). This IDBRequest has a .source
which is the IDBIndex object. Is that enough from the cursor to the
index? I don't feel strongly.

/ Jonas
Received on Friday, 28 January 2011 04:05:44 GMT

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