W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2015

Re: What happened to onaddstream?

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Wed, 24 Jun 2015 07:09:03 +0000
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
CC: Harald Alvestrand <harald@alvestrand.no>, Martin Thomson <martin.thomson@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>, Peter Thatcher <pthatcher@google.com>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D28A932@ESESSMB209.ericsson.se>
On 23/06/15 13:07, Silvia Pfeiffer wrote:

> I did some more digging.
> Reading the spec, I stumble over both an ontrack and an onaddtrack
> event. The ontrack event is used in Example 4 to replace the
> onaddstream event from earlier on the RTCPeerConnection. The
> onaddtrack fires on MediaStream directly.
> So, we're really talking about the ontrack event here.


> It seems to me that ontrack has the exact same definition as
> onaddstream, except it is a RTCTrackEvent (and not a MediaStreamEvent)
> and can report the addition of multiple MediaStream objects in one go.
> http://w3c.github.io/webrtc-pc/#idl-def-RTCTrackEvent
> I'm actually a bit confused about this description: it seems that a
> track can be part of multiple streams there. That's not how I
> understand MediaStreams to work - rather, a track would always be part
> of one stream, but a stream could have multiple tracks.

I think both ways are OK. A MediaStream is basically a collection of 
MediaStreamTrack's, but a MediaStreamTrack can be part of more than one 

Just assume you have MediaStream's A and B, and a MediastreamTrack X, 
AFAIK nothing forbids


Received on Wednesday, 24 June 2015 07:10:08 UTC

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