- From: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Feb 2017 13:41:59 +0000
- To: public-device-apis-log@w3.org
I was planning to have an internal data structure that is being fulfilled periodically (using a timer) with N latest readings starting from the moment when `collectLatestReadings()` is called and till the moment when next frame paint is scheduled (i.e. right before rAF callbacks are invoked) and in the later moment the internal data structure contents would be copied to the given `Float64Array`. Thus client has a notion of previous readings obtained with the frequency higher than the current frame rate. In Chromium sensor data is fetched from the underlying system in one process and then it is put to a shared memory buffer. JS runs within a different process. Considering the fact that JS engine can arbitrary pause or defer scripts execution I doubt that we can completely avoid sample loosing whatever API we invent. -- GitHub Notification of comment by pozdnyakov Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-282293668 using your GitHub account
Received on Friday, 24 February 2017 13:42:06 UTC