- From: Jafar Husain via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Jun 2015 20:30:57 +0000
- To: public-device-apis@w3.org
I respect your experience in this area, and it's great to have these real world use cases to consider. If the main mechanism of composing together signals is indeed through examining variables fed at high velocity that's a great data point. Composition would be more interesting if other asynchronous actions like network requests or animations were ever kicked off/cancelled by signals. Then you would have concurrency to coordinate. However if use cases for composition around sensors are really that rare, developers could always adapt an eventtarget to an observable in those instances. I am concerned about choosing a type to model sensors that does not have a completion semantic, but if you're confident that it is unnecessary that's valuable feedback. What about error handling? Are there cases in which a sensor stream might terminate due to an error? Is this marginal a case as well? -- GitHub Notif of comment by jhusain See https://github.com/w3c/sensors/issues/21#issuecomment-108089768
Received on Tuesday, 2 June 2015 20:30:59 UTC