Tobie Langel

Thanks for the issue and use cases and thoughts on the topic. This is unfortunately out of scope for V1. I'm keeping it open for V2.

Thanks a lot for reaching out. I'll have a look at these.

Would love input from all and in particular from the following: @annevk , @anssiko, @borismus, @domenic, @dontcallmedom, @fhirsch, @marcoscaceres, @mfoltzgoogle, @riju, @richtr, @rwaldron, @timvolodine.

Re @rwaldron's [comment](https://github.com/w3c/sensors/issues/88#issuecomment-192967025): > If the processor and sensor hub are powered, then hardware is already active. Well, sensors aren't running all the time. They consume a lot more battery...

Re @anssiko's [comment](https://github.com/w3c/sensors/issues/88#issuecomment-192972157): > Just noting the `MessagePort` has this interesting (not very intuitive IMO) behaviour: > > > ... when using `addEventListener()`, the `start()` method must also be invoked....

@rwaldron to be totally fair, I thought I came up with solution 3. So now that you pointed out it wasn't my idea, I've started to like it better. :)

re @rwaldron's [comment](https://github.com/w3c/sensors/issues/88#issuecomment-193002528): Just for kicks changed your first example with a sensor born deactivated (as in iOS, for example) and that has `activate`/`deactivate` instead of `resume`/`pause`. _On second thought...

Re @darobin's [comment](https://github.com/w3c/sensors/issues/88#issuecomment-193003582): > So, I might be missing something here but would it be wrong to have a sensor being active when it has event listeners and deactivated when...

> Considering the amount of boilerplate crap involved in both the Android version and iOS version, I think whatever we choose will be better. That sums it up pretty well....

re @darobin's [comment](https://github.com/w3c/sensors/issues/88#issuecomment-193281097): > @tobie I've been out of the loop for a while, but is the `rAF` example realistic (and fundamental)? Yeah, it seems like a common use case...