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

@tidoust 

> Just to make sure I got that right. A TVSource in this model creates
 at most one stream. An app won't be able to tune to multiple channels
 at once using the same TVSource, even if it calls tuneToChannel 
multiple times. It needs two TVSource instances for that to be 
possible. Is that correct?

Yes

> When would the user be prompted for permission in regular web 
applications (type 3)? As a result of a call to getSource? That seems 
needed not to leak information about available sources to arbitrary 
origins.

Good question :)  I havent thought about this much, but my first 
reaction is that a call to getSource() is what should trigger 
prompting the user for permission.  It doesn't leak information on its
 own, but it's probably a the best gatekeeper to privileged 
functionality (tuning, getting a channel list, etc.) that lets us 
minimize the number of prompts to the user.

> Delivery type makes sense as a criterion for users to grant 
permission ("this app wants to access your FM radio, do you agree?"). 
Quality level does not make a lot of sense ("this app wants to access 
your HD channels, do you agree?"). We may want to mandate the delivery
 type constraint to avoid asking the user too generic a question 
("this app wants to access your broadcast signals, do you agree?"). 
Once user grants permission for an app to access a specific delivery 
type, permission can probably be assumed for further calls to 
getSource (and isSourceAvailable) for that same delivery type.

Yes, but mandating the delivery type means that an application *has* 
to care about this, when it otherwise may not.  We may want to say 
that if a delivery type isn't specified then the user agent may prompt
 to give access to all delivery types, but I'm not sure if that's a 
good idea or not - I havent thought about it enough.

> Also, the user would not be asked for permission to access a 
particular channel if it gets prompted after the call to getSource, 
unless we ask her again when calling to tuneToChannel. Or do you 
envision that the channel name could be one of the constraints that 
could be provided to getSource? This may be an edge case, I do not 
know whether apps will only want to tune in to one particular channel.

I thought about supplying the channel name as one of the constraints, 
but that then gets complicated (e.g. if you know the tuning 
parameters, can you tune directly to that channel?).  As we've 
mentioned elsewhere, you could use constraints as a way of tuning - to
 change channel, you apply a new set of constraints - but that is 
something that needs more thought and still seems a little unnatural 
to me (although with this model, it's becoming less unnatural...)

-- 
GitHub Notification of comment by stevem-tw
Please view or discuss this issue at 
https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-273217697 
using your GitHub account

Received on Tuesday, 17 January 2017 16:21:42 UTC