- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2017 10:18:29 +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. > I'd say it's rather closer to (3), the whole sequence is kept, nothing is lost You're right. So I don't think it's a good model for our use cases. The use case I imagined for (3) where those which involved over-the-network processing, tolerated much higher latency and were expecting much larger batches of sensor readings. Scenario (2) really looks at > 60 readings per second real time use cases (where you're not increasing polling speed in the sole goal of reducing latency). -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-299829219 using your GitHub account
Received on Monday, 8 May 2017 10:18:35 UTC