Should update sensor reading task be in sync with latest reading?

[alexshalamov]

When sensor reading is changed, new ‘update sensor reading’ task is scheduled. When queued task is executed, last reading might change from the time when task was created.

Should 'update sensor reading task' use reading at the time of task creation or 'latest reading' when task is executed? (in Chromium we do latter, might reduce latency due to queue processing delay)

Would be good to reflect that in spec.

[tobie]

Should 'update sensor reading task' use reading at the time of task creation or 'latest reading' when task is executed? (in Chromium we do latter, might reduce latency due to queue processing delay)

The former. The whole point of this exercise is to avoid the latter case which might create concurrency issues.

What's the extra latency like from the queued stuff? Totally application-level code dependent?

[alexshalamov]

What's the extra latency like from the queued stuff? Totally application-level code dependent?

If browsing context has multiple queues from different sources, there might be priorities for processing those queues, right?

[tobie]

If browsing context has multiple queues from different sources, there might be priorities for processing those queues, right?

Yeah, that's a good point. I have absolutely no idea how this is organized, either in spec-land or in implementations.

Filed #221 so we can look at it at a later point. From an architectural perspective of the spec, leaving this out now makes it easier to make progress.

[alexshalamov]

@tobie According to resolved #8 and the specification, Sensor.|reading| always points to platform sensor 'latest reading'.

@pozdnyakov added more comments to #152

[tobie]

According to resolved #8 and the specification, Sensor.|reading| always points to platform sensor 'latest reading'.

How is that relevant to this issue?

[tobie]

OK, as comments about #8 seem irrelevant to this issue, and issue itself is essentially a question about how tasks works. I'm closing this. Feel free to re-open if I missed something.