Tobie Langel

OK, so have `event.data` always be a reverse-chronological array of sensor values (all values since the previous event, I suppose?). Isn't that unnecessarily wasteful in case only the last value...

> Yes in this snippet event.data is reverse-chronological array of sensor values since the previous event. Are you saying it's wasteful to have an array with one value in it?...

There seems to be solid use cases and broad agreement to provide batches of sensor values when the frequency of `onchange` events is below the frequency at which the data...

My understanding from https://github.com/w3c/sensors/issues/9#issuecomment-63326257 is that a batch mode is necessary for performance reasons (due to the cost of re-entering the JS context every time the sensor emits a value)....

> My concern still stands: what if the batch is 104400000 accelerometer snapshot objects? There are various solutions to that I guess, e.g. a maximum configurable amount of historical sensor...

Updated the proposed resolution and next actions following your comments, @rwaldron: **Proposed resolutions:** Some use cases have high data frequency requirements which might cause performance and/or memory constraints. Further research...

From a developer experience perspective, I don't think that's an optimum solution, as now you have to figure out whether your option is immutable or not. Given extra options won't...

Seems there's approval in the [October 2015 minutes](https://lists.w3.org/Archives/Public/public-device-apis/2015Oct/att-0037/minutes-2015-10-15.html#item05).

@dontcallmedom can you help with this? Or point me to the right direction? Thanks!

:dancer: