- From: David Bruant <bruant.d@gmail.com>
- Date: Wed, 07 Nov 2012 09:01:00 +0100
- To: Jonas Sicking <jonas@sicking.cc>
- CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
Le 07/11/2012 08:27, Jonas Sicking a écrit :
> On Tue, Nov 6, 2012 at 11:35 AM, David Bruant <bruant.d@gmail.com> wrote:
>> Hi,
>>
>> The WebAPI team at Mozilla defined the DeviceStorageAPI [1] which contains
>> the following:
>> interface DeviceStorage {
>> /* ... */
>> // See interface below for how to use this
>> DeviceStorageCursor enumerate(optional DOMString directory)
>> DeviceStorageCursor enumerateEditable(optional DOMString directory)
>> };
>>
>> interface DeviceStorageCursor : DOMRequest {
>> void continue();
>> };
>>
>> It really feels like an ES6 generator [2]. Is it possible to add a new
>> keyword that would allow people defining WebIDL interfaces to define
>> generators so that we have consistent interfaces between ES code and web API
>> code? For the ECMAScript binding, this keyword would obviously refer to an
>> generator.
>>
>> David
>>
>> [1] https://wiki.mozilla.org/WebAPI/DeviceStorageAPI
>> [2] http://wiki.ecmascript.org/doku.php?id=harmony:generators
> Note that the DeviceStorage cursor, just like the IndexedDB cursor, is
> completely asynchronous. So it doesn't really map well to ES6
> generators or iterators.
Ooh... I guess I misunderstood the API then. My bad.
David
Received on Wednesday, 7 November 2012 08:01:32 UTC