- From: Steve Morris via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Aug 2016 10:06:24 +0000
- To: public-tvcontrol@w3.org
> Intuitively, I would prefer a tuner with multiple `TVSource` to behave as a tuner with only one `TVSource`. Other than for informational purpose (which could be returned as part of the channel's metadata), why would a Web app developer need to know that a tuner may switch between multiple sources? A Web app developer may not care, but this is a decision that has a substantial impact on how you would implement the API. At the moment, things like channel lists and logical channel numbering and channel scanning are managed on a per-source basis. If you removed the concept of a `TVSource` then the implementation would have to provide a single channel list that is merged from all sources. However, this would have a number of complications: - channel numbering schemes may not be consistent across sources - channel scanning may have different performance issues or algorithms depending on different sources - the same channel may be present on multiple sources, which may lead to a unified channel list having several instances of the same channels. Without specifying the behaviour in extreme detail, it's not really possible to guarantee that multiple implementations would give consistent results, and TV and STB manufacturers would probably object to that, given that they already have implementations of this functionality that they would be very reluctant to modify. -- GitHub Notification of comment by stevem-tw Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-239769437 using your GitHub account
Received on Monday, 15 August 2016 10:06:30 UTC