Batching and sending over bluetooth seems to be a candidate for option (3) above with lower latency requirements. What I'm really interested in is browser-based rAF-tied use cases with low-latency requirements and bigger than 1 reading per frame requirements. Afaik, some of the newer work on VR has such requirements (i.e. they're using all readings between frames, not just the freshest one). As this has API design impact and buffer structure impact, it's important that we look at it now. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-299466394 using your GitHub accountReceived on Friday, 5 May 2017 13:36:48 UTC
This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC