W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2014

Re: DAP-ISSUE-169: Battery API needs to be more event driven and async, less device centric. [Battery Status API]

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Fri, 8 Aug 2014 09:29:03 -0400
Cc: Frederick Hirsch <w3c@fjhirsch.com>, Device APIs Working Group <public-device-apis@w3.org>
Message-Id: <FB47DD63-A51F-476C-B135-9FF07C70F27C@fjhirsch.com>
To: Mounir Lamouri <mounir@lamouri.fr>
That is a very good question, but the issue was dated 6 Aug 2014 so I *assume* it was for the latest promises based spec (but you know what happens when you assume). 

We are not exactly sure what this comment means concretely and Lisa is asking for clarification (and a concrete proposal if needed) - part of that is to make sure we have the correct context for this issue.

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Chair DAP
@fjhirsch



On Aug 8, 2014, at 9:18 AM, Mounir Lamouri <mounir@lamouri.fr> wrote:

> On Fri, 8 Aug 2014, at 06:46, Device APIs Working Group Issue Tracker
> wrote:
>> DAP-ISSUE-169: Battery API needs to be more event driven and async, less
>> device centric. [Battery Status API]
>> 
>> http://www.w3.org/2009/dap/track/issues/169
>> 
>> Raised by: Lisa Seacat DeLuca
>> On product: Battery Status API
>> 
>> on behalf of Joe Bowser
>> 
>> 'The spec is flawed in that there's no way we could implement it as it
>> stands. The spec needs to be reworked to be more event driven and
>> asynchronous.   Right now it's too much like device with everything up
>> front."
> 
> Does that issue apply to the current version of the API?
> 
> -- Mounir
> 
Received on Friday, 8 August 2014 13:29:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:11 UTC