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

RE: comments of sensor API

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Mon, 19 Mar 2012 17:30:58 +0000
To: ÕųÉÑÒ <zhangcy@chinaunicom.cn>, public-device-apis <public-device-apis@w3.org>
Message-ID: <84BCA539DD96614691177EDA3CE4FF054525F908@ORSMSX101.amr.corp.intel.com>
Hello,
As soon as the ¡°endWatch¡± function is called, the watching process is stopped and the app will not get any more events, so in your case the ¡°SensorWatchOption¡± is no longer effective. The app can still do a ¡°read¡± or start a new watch point with ¡°startWatch¡±.

Thanks, Tran

From: ÕųÉÑÒ [mailto:zhangcy@chinaunicom.cn]
Sent: Sunday, March 18, 2012 6:46 AM
To: public-device-apis
Subject: comments of sensor API

Hi,all
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:
[cid:image001.jpg@01CD05BA.C6ACED10]

2012-03-18
________________________________
 CHINA UNICOM RESEARCH INSTITUTE
Terminal Research and Support Centre
Chengyan Zhang
mob£º18601103800


image001.jpg
(image/jpeg attachment: image001.jpg)

Received on Monday, 19 March 2012 17:31:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:53 UTC