Re: [tvcontrol-api] API surface and REST-based approach

One more aspect that I overlooked in my previous comment.

A `MediaStream` does not directly give access to flows of bytes. It 
provides a handle to associate a source with sinks (e.g. <video> 
tags). The underlying flows of bytes can (and will) take direct routes
 between the source and the sinks, and in particular they do not need 
to be copied over in memory or in any application-visible space. 
Having to copy bytes around is costly in terms of performance (CPU, 
power, memory, and time).

For instance, in TV/radio sets, I suppose that the decoding pipeline 
directly connects the tuner to the graphics card for rendering. And I 
suppose it is a feature.

I'm not sure how to achieve this in the **external source-centric** 
model. If the TV box is to be an external endpoint from the 
perspective of the user agent, then the user agent needs to fetch the 
bytes somehow before it renders them.

If we want user agents not to fetch the bytes, then we need some way 
for them to connect directly to the internals of the supposedly 
external TV box... I believe that defeats the main purpose of the 
external model. Essentially, we're back to the internal model. Or is 
there a simple way to achieve this while preserving a clean separation
 between the TV box and the user agent?



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

Received on Thursday, 1 December 2016 10:28:52 UTC