Yes, (3) is for the #98 use case. Given those are essentially going to be sent over the network for further analysis, it might be worth aiming for something as fetch/stream-compatible as possible (Which afaik typedarrays are pretty good for too). We'll probably want reporting frequency to be very different from polling frequency in such cases, so maybe a completely different API for this? For (2), on the other, we want something closer to (1) in API terms, so you can really easily move from dealing with a single data point to multiple ones. -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/171#issuecomment-299833606 using your GitHub accountReceived on Monday, 8 May 2017 10:41:33 UTC
This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC