- From: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2017 10:06:12 +0000
- To: public-device-apis-log@w3.org
> The newly proposed getCoalescedEvents PointerEvent extension is very similar to our option (2) here. Worth digging deeper.
Yeah, getCoalescedEvents-like approach is most likely a solution for batching for us (and this is what I concluded from my investigation, pls. see https://github.com/w3c/sensors/issues/171#issuecomment-288113690). My point is that batching API should be an _extension_ to the existing sensor properties, i.e. we should not try to substitute the the existing `sensor.{timestamp, x, y, z}` with some API providing all the reported readings and at the same time trying to still keep minimal latency.
--
GitHub Notification of comment by pozdnyakov
Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-299826599 using your GitHub account
Received on Monday, 8 May 2017 10:06:19 UTC