RE: ACTION-119: on how to define the availability of properties

Just a thought:

The use case for watching a activeness of a network interface on a mobile phone could be:
 If my WiFi is active then I know that the system/OS is switching me from 3G data to WiFi, now I know that I am not charge for data and my application can provide some service based on that fact.


Also from the latest spec, I can't tell if Network is enumerable. The figure and text associated with Network does not seem to indicate so. Maybe I am missing something.

Thanks
Dzung Tran


-----Original Message-----
From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Dominique Hazael-Massieux
Sent: Tuesday, March 23, 2010 10:34 AM
To: Max Froumentin
Cc: public-device-apis@w3.org
Subject: Re: ACTION-119: on how to define the availability of properties

> Option 1 is
> + easier to define (only needs 1 interface)
> + allows more than one device to be active (not sure if that's useful)

FWIW, option 2 can be made to support more than one device as well by
making the property an array rather than a scalar.

> - makes it harder for the webapp writer to access the active device
> + lets you watch the active-ness of a specific device
> 
> What do people think?

The first pro is only making our life easier, so I think it needs to be
considered very last; I don't think the second one really distinguishes
the two proposals; I'm not very convinced that there are large use cases
for watching activeness of a specific device; as a result, my feeling is
that option 2 is probably better.

Another option would be to add "available" (or "active") as a parameter
in the system.get() call, probably with a specialized Options interface
for those of the relevant properties that can be active or not.

Dom

Received on Tuesday, 23 March 2010 22:42:41 UTC