W3C home > Mailing lists > Public > public-device-apis-log@w3.org > November 2016

Re: [sensors] Call onchange only when data changes

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Fri, 11 Nov 2016 13:45:53 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-259960187-1478871952-sysbot+gh@w3.org>
> The way onchange is described now would fit more to an event handler
 called onreadingupdate or onnewreading

I agree. But that's been argued against a number of times (and I lost 
these arguments). Terseness trumped correctness here.

> and thus it is conflicting with the requirement of shared reading 
instance as supposed to be called simultaneously for all the sensor 
instances.

Yes, that's a good point. This wasn't an issue before, as I thought 
implementers were not going to be willing to send events are different
 frequencies to the different instances for perf reasons (and 
implementation complexity).

> Can we just specify that onchange is called:
> 1) when the data is actually changed

Some use cases (notably motion sensors) might need data sent at 
regular intervals regardless of whether the sensor values changed, 
we'll need to dig into this a bit more.

> 2) not more often than the given frequency

That's the Android way mentioned above and might be the reasonable 
thing to do.

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/152#issuecomment-259960187 using
 your GitHub account
Received on Friday, 11 November 2016 13:45:59 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:53 UTC