- From: Doug Turner <w3c@dougt.org>
- Date: Mon, 4 Jan 2010 09:07:54 -0800
- To: Max Froumentin <maxfro@opera.com>
- Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>
>> 2) Maybe we can roll get and watch together into one api. I am not
>> sure the value of having two different methods are -- one for one
>> time shot, and one for watching changes.
>
> like
>
> get("PowerLevel", success, error)
>
> and
>
> get("PowerLevel", success, error, {watch: true});
>
> for instance? Why not. But I think that the current way makes it clearer that both types of operations are possible, rather than the watch feature being buried inside the options parameter. What was geolocation's reason for having both get and watch?
I suppose you are right; having both a get and a watch makes this design much simpler.
>> 14) Have you considered adding the MAC address of the router to
>> Connection? (use case: WiFi positioning).
>
> No. To be honest I didn't add too much there because I expect expert to tell me what's best to have. So I've added it. But just to make sure I'm understanding you right, you are suggesting adding something like
> "readonly DOMString MacAddress" to Connection, right?
Yes, and we need to define its format. Eg. it should always be in the form of xx:xx:xx:xx:xx:xx.
Received on Monday, 4 January 2010 17:08:25 UTC