- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2017 10:14:24 +0000
- To: public-device-apis-log@w3.org
@pozdnyakov from our previous conversations, the latency issue only appeared if we added the requirement *not to loose any intermediary reading* to our API. (2) above is clearly distinct in that regard and it seems that there are potential use cases for this fast with more than 1 reading per rAF scenario. Additionally, creating this API at a later stage does not absolve us from the necessity of designing our API today so that it is compatible with that future design and stays developer friendly. For example, if such an API is buffer-based, we'll need a way to express timestamps within buffers. Maybe this is something worth considering upfront. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-299828353 using your GitHub account
Received on Monday, 8 May 2017 10:14:30 UTC