[tvcontrol-api] Why retrieve a list of tuners instead of just one tuner?

tidoust has just created a new issue for 
https://github.com/w3c/tvcontrol-api:

== Why retrieve a list of tuners instead of just one tuner?  ==
The main entry-point of the TV Control API is the retrieval of a list 
of tuners through the `getTuners` function.

I would have assumed that, leaving recorders aside for a moment, most 
devices ship with only one tuner, or at least one tuner of given kind 
(radio/tv). What are the use cases that drive the need to expose a 
list of tuners? Are there common products that feature multiple 
tuners?

What can a Web app do with the list of tuners it gets from 
`getTuners`? It cannot easily ask the user to select a tuner for 
instance, because all it has to describe the tuner is an ID which most
 probably won't mean anything to the user.

I wonder whether that function should not be replaced by a `getTuner` 
function that could possibly take a filtering rule as parameter and 
would return one `Tuner` instance. The user agent is likely going to 
prompt the user for permission to access the tuner when this call is 
issued in any case, so it could also use that opportunity to ask the 
user to select the tuner to expose to the Web app if different tuners 
are available.

Note that I left tuners used for recordings aside because the spec 
treats them separately as well.


Please view or discuss this issue at 
https://github.com/w3c/tvcontrol-api/issues/4 using your GitHub 
account

Received on Monday, 11 July 2016 10:55:33 UTC