W3C home > Mailing lists > Public > public-media-capture@w3.org > April 2013

Re: addTrack/removeTrack on gUM streams and PeerConnection remote streams

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Wed, 17 Apr 2013 12:18:56 +0200
Message-ID: <516E7710.2010205@ericsson.com>
To: robert@ocallahan.org
CC: Stefan HÃ¥kansson LK <stefan.lk.hakansson@ericsson.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2013-04-17 12:15, Robert O'Callahan wrote:
> On Wed, Apr 17, 2013 at 10:06 PM, Adam Bergkvist
> <adam.bergkvist@ericsson.com <mailto:adam.bergkvist@ericsson.com>> wrote:
>     The model to let an application-managed MediaStream
>     (BundleMediaStream) inherit from MediaStream is simple but gives us,
>     IMO, a lot. The only drawback I can see is that the event handlers,
>     used to listen to how the UA adds and removes tracks, are available
>     on BundleMediaStream as well. We could add a new common base type to
>     get around that, but I don't think it's a deal breaker.
> I'm confused. What's the problem with the event handlers? They would
> remain on MediaStream.

Since they're only used to listen to when the UA updates the track set 
they wouldn't be used when it's only the application that manages the 
track set.

This is a bit confusing in the current spec. The description of the 
events say that they are fired whenever a track is added, which is 
misleading since they are not fired in the addTrack()/removeTrack() 
algorithms. It's fixed for the next release.

Received on Wednesday, 17 April 2013 10:19:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:16 UTC