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

Re: [IndexDB] Proposal for async API changes

From: Nikunj Mehta <nikunj@o-micron.com>
Date: Tue, 22 Jun 2010 00:59:01 +0800
Cc: Jonas Sicking <jonas@sicking.cc>, Webapps WG <public-webapps@w3.org>
Message-Id: <31E5B2B6-B2F8-4DF8-AB94-DFBC0B8C4FF8@o-micron.com>
To: Andrei Popescu <andreip@google.com>

On Jun 22, 2010, at 12:44 AM, Andrei Popescu wrote:

> On Tue, Jun 15, 2010 at 5:44 PM, Nikunj Mehta <nikunj@o-micron.com> wrote:
>> (specifically answering out of context)
>> 
>> On May 17, 2010, at 6:15 PM, Jonas Sicking wrote:
>> 
>>> 9. IDBKeyRanges are created using functions on IndexedDatabaseRequest.
>>> We couldn't figure out how the old API allowed you to create a range
>>> object without first having a range object.
>> 
>> Hey Jonas,
>> 
>> What was the problem in simply creating it like it is shown in examples? The API is intentionally designed that way to be able to use constants such as LEFT_BOUND and operations like only directly from the interface.
>> 
>> For example,
>> IDBKeyRange.LEFT_BOUND; // this should evaluate to 4
>> IDBKeyRange.only("a").left; // this should evaluate to "a"
>> 
> 
> But in http://dvcs.w3.org/hg/IndexedDB/rev/fc747a407817 you added
> [NoInterfaceObject] to the IDBKeyRange interface. Does the above
> syntax still work? My understanding is that it doesn't anymore..

You are right. I will reverse that modifier.

Nikunj
Received on Monday, 21 June 2010 17:07:36 GMT

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