W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2013

Re: Using tracks instead of streams

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 12 Nov 2013 00:54:21 -0800
Message-ID: <CABkgnnXG5oXEw1Auipm4iGcpCTPqX7DkjDFvUDintF4-pVMo6w@mail.gmail.com>
To: Adam Bergkvist <adam.bergkvist@ericsson.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 12 November 2013 00:18, Adam Bergkvist <adam.bergkvist@ericsson.com> wrote:
> One thing that I find a bit odd is:
>
> pc.addSendTrack(track);
> pc.sendTracks[0] == track; // false (different types)

It's more like:

pc.addSendTrack(track) === pc.sendTracks[0];

> We could have the script construct a DooHickey and add it to the
> PeerConnection.
>
> // A-side
> var hickey = new DooHickey(track);
> peerConn.addDooHickey(hickey);

That seems like busy work.  It also means that you can't make the
special linkage that a Doohickey needs with RTCPeerConnection.

> // B-side
> ondoohickey  = function (evt) {
>   hickey = evt.dooHickey;
>   remoteVideo.srcObject = new MediaStream([hickey.track]);
> };

I see no reason that evt.track doesn't point to the track.  AND,
track.streams[0] should be populated with a newly created stream.
Received on Tuesday, 12 November 2013 08:54:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:36 UTC