W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2012

comments of sensor API

From: 张成岩 <zhangcy@chinaunicom.cn>
Date: Sun, 18 Mar 2012 21:45:56 +0800
To: public-device-apis <public-device-apis@w3.org>
Message-ID: <201203182145560071147@chinaunicom.cn>
Here is a question about the attributes of  “SensorWatchOptions”:
The “interval” attribute and” threshold” attribute of  “SensorWatchOptions” are transferred when “startWatch” function is called. But I do not find how to deal with them when “endwatch” function is called. So my question is : “Is “SensorWatchOption” still effective after the “endwatch” function was called?” if still effective, I am afraid that it would adversely increase the power consumption.
    According to the specification, the sensor is always open after the “SensorConnection” was created. But to the developers of browser, it is very important to know when the sensor was open and when the sensor was closed. So my suggestion is that the process and status of sensor should be amended to resolve this problem. Details are as below:


Terminal Research and Support Centre
Chengyan Zhang

(image/jpeg attachment: Catch0.jpg)

Received on Monday, 19 March 2012 07:36:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:35 UTC