- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Feb 2017 13:48:33 +0000
- To: public-device-apis-log@w3.org
>From the feedback gathered so far here, it seems a _reporting frequency_ whose max is tied to the animation frame rate is sufficient. On the other hand, a faster _polling frequency_ seems necessary to either: 1. gather more data points (indoor navigation use case), or 2. decrease latency (VR use case). There are privacy concerns with sampling > 60 Hz, though my understanding is research by @maryammjd seems to indicate this is an issue at much lower frequency rates already. (@maryammjd can you please confirm, plus point to relevant papers?) When _polling frequency_ is higher than _reporting frequency_ and we don't want to loose samples (so not the VR case), we need to buffer samples. This needs discussion as to how best to achieve this. BYOB? Dedicated API? Etc. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/98#issuecomment-281083570 using your GitHub account
Received on Monday, 20 February 2017 13:48:41 UTC