W3C home > Mailing lists > Public > public-media-capture@w3.org > September 2012

Re: The MediaStream constructor

From: Anant Narayanan <anant@mozilla.com>
Date: Tue, 25 Sep 2012 08:16:52 -0700
Message-ID: <5061CAE4.7050408@mozilla.com>
To: "Tommy Widenflycht (ᛏᚮᛘᛘᚤ)" <tommyw@google.com>
CC: public-media-capture@w3.org
On 9/24/2012 11:36 AM, Tommy Widenflycht (ᛏᚮᛘᛘᚤ) wrote:
> Well, a MediaStreamTrackList is fine as well :)
>
> The difficult to implement thingie is the "union of MediaStream,
> MediaStreamTrackList and MediaStreamTracks".

It is either MediaStream or MediaStreamTrackList. It should not be 
possible to create  a new MediaStream using only MediaStreamTracks 
(without first wrapping them in a list).

Cheers,
-Anant

> On Mon, Sep 24, 2012 at 7:20 PM, Anant Narayanan <anant@mozilla.com
> <mailto:anant@mozilla.com>> wrote:
>
>     Hi Tommy,
>
>
>     On 9/24/12 4:25 AM, Tommy Widenflycht (ᛏᚮᛘᛘᚤ) wrote:
>
>         I have started planning implementing the latest MediaStream
>         constructor
>         in WebKit but it is difficult and complex to implement. Changing
>         it to
>         take an array of MediaStreamTracks would simplify it significantly
>         without making life harder (not by much anyway) for the web
>         developer.
>         Opinions?
>
>
>     This was proposed earlier, but Rich made a good argument for why it
>     shouldn't be an array:
>     http://lists.w3.org/Archives/__Public/public-media-capture/__2012May/0017.html
>     <http://lists.w3.org/Archives/Public/public-media-capture/2012May/0017.html>
>
>     What specifically is the difficulty in taking a MediaStream
>     MediaStreamTrackList instead of an array?
>
>     Cheers,
>     -Anant
>
>
>
>
Received on Tuesday, 25 September 2012 15:18:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:01 GMT