- From: Steve Morris via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Jan 2017 10:09:31 +0000
- To: public-tvcontrol@w3.org
@chrisn Thanks for your comments > We've discussed a few names so far for the idea of "the set of resources dedicated to providing a stream" - TVTuner, Player, Session, and now TVSource. I think my preference is still for Session, although I'd probably name the interface TVMediaSession, which might help distinguish it from "session" as in cookies. But that said, I don't feel too strongly. I would be happy with this, partly because it gets us away from existing names and stops us making any assumptions. > > I think that simply getting a TVSource does not allocate any scarce resources: this only happens when a source is tuned to a channel. > Yes, I agree. There are some consequences of this approach, but I think we can deal with those. If we say that we have a method or methods that tunes to a channel (which allocates resources) and a method which stops the session (which stops streaming the channel and deallocates any resources) then this is probably OK, but it is slightly different from the way that is used by the Media Capture and Streaming API. > We'll also need to think about how we handle channel scanning in this new API structure. This is currently done on a per-source basis, so would we still need a TVSource interface (as currently written in the spec), and the ability to enumerate sources? (We should probably discuss this under issue #7; it may depend on whether we need to expose an API for scanning at all). I'm inclined to say that we move the scanning API to the TVManager interface and say that scanning applies to the device as a whole, not a particular source. This has the advantage of meaning that the user agent (or other external software components) are responsible for managing the channel list and handling how channel lists from different sources are merged and ordered. > Finally, would we need the `isSourceAvailable` method? I imagine the main use case for this is to check whether a subsequent call to `getSource` will succeed, which we can handle through the returned promise. Are there other use cases I've missed? I'm not sure - I need to think about this a little more, if people think that this is a good way forward. Steve. -- GitHub Notification of comment by stevem-tw Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-273082428 using your GitHub account
Received on Tuesday, 17 January 2017 10:09:37 UTC