Re: RE: comments of sensor API

Hi,Tran
   Thank you very much for your explain.I still have another question, does the app have the ability to open and close the sensor?  According to the specification, the sensor is always open after the “SensorConnection” was created. i am not sure if i misunderstand it or not

2012-03-20 



CHINA UNICOM RESEARCH INSTITUTE 
Terminal Research and Support Centre
Chengyan Zhang
mob：18601103800



发件人： Tran, Dzung D 
发送时间： 2012-03-20  01:31:05 
收件人： Chengyan Zhang(联通集团中国联合网络通信集团有限公司研究院); public-device-apis 
抄送： 
主题： RE: comments of sensor API 
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:

 
2012-03-18 



 CHINA UNICOM RESEARCH INSTITUTE 
Terminal Research and Support Centre
Chengyan Zhang
mob：18601103800