W3C home > Mailing lists > Public > public-media-capture@w3.org > December 2011

RE: Thoughts on converging MediaStream and Stream objects

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Fri, 9 Dec 2011 21:52:43 +0000
To: Harald Alvestrand <harald@alvestrand.no>
CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B38381C75BA@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
>-----Original Message-----
>From: Harald Alvestrand [mailto:harald@alvestrand.no]
>
>I think you are misled by an accident of naming.
>
>If anything should be converged with the Stream API (something I'm not
>at all sure of), it should be the MediaStreamTrack.
>
>The sharpest difference is that a Stream is a byte pipe; a
>MediaStreamTrack is a control surface for an underlying implementation
>where the concept of "byte" doesn't even have to be meaningful.

I certainly understand the difference between the MediaStreamTrack 
and the Stream-as-a-byte-pipe, however I didn't make the connection to
why/how you think the two should be converged? Can you explain in more
detail?
Received on Friday, 9 December 2011 21:53:21 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:14:58 GMT