- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Jan 2017 14:36:40 +0000
- To: public-tvcontrol@w3.org
Trying to capture main feedback received from the Media Capture Task Force (additional notes are from me): 1. General agreement that attaching to `enumerateDevices` seems a bad idea 2. Attaching to `mediaDevices` is still doable. I note that having a dedicated `TVManager` interface allows us to add other methods and properties at that level, which we seem to need. If we end up with an empty interface for some reason, we can always decide to re-attach to `mediaDevices` later on. 3. General agreement that using `MediaStreamTrack` constraints to switch to another channel seems a bad idea. 4. Streams are lightweight and are just a control surface. We could consider revisiting our decision to reuse streams across channels. I suspect the main arguments in favor/against reuse will be linked to locking the underlying resources. 5. Do we need MediaStreams at all? If we don't really plan to use constraints at the track level, we could just as well adopt a design similar to Media Source Extensions and attach to media elements directly. 6. Adding a `stop` method at the stream level seems a bad idea 7. `isRecordable` could perhaps be implemented by assigning a random identity at the streams level (?) -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-273183553 using your GitHub account
Received on Tuesday, 17 January 2017 14:36:51 UTC