Re: [sensors] Batching API for sensor readings

On the call we had today, @pozdnyakov suggested we completely drop the API that collects 
the latest few readings while still keeping low latency. That's our option 2 described in https://github.com/w3c/sensors/issues/171#issuecomment-288044722, which relies on collecting multiple readings in a single buffer.

iirc we had use cases and requirements for this API, but I wasn't sure what they were precisely. @kenchris, @rwaldron, do you have any in mind or is it OK to limit the number of readings exposed in realtime to a maximum of 1 reading per rAF?

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-298981461 using your GitHub account

Received on Wednesday, 3 May 2017 17:35:43 UTC