Re: addTrack/removeTrack on gUM streams and PeerConnection remote streams from Adam Bergkvist on 2013-10-07 (public-media-capture@w3.org from October 2013)

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Mon, 7 Oct 2013 13:30:06 +0200
To: Harald Alvestrand <harald@alvestrand.no>
CC: <public-media-capture@w3.org>
Message-ID: <52529B3E.4050406@ericsson.com>

On 2013-09-27 14:28, Harald Alvestrand wrote:
> Reawakening an old discussion (tracked in bug 22270).
>
> The suggestions made are (I think) three different ones:
>
> - Create two classes of MediaStream, one which adds tracks under UA
> control, and one which adds tracks under Javascript control. Only the
> second has the addTrack and removeTrack methods. getUserMedia and
> peerconnections produce the first type.

I think we should give this approach a try. We would get a Stream API 
with better structure and separation of responsibilities (UA vs script). 
I think that's better to build upon if we need to extend the Stream API 
in the future.

/Adam

> - Let addTrack and removeTrack fail when a MediaStream comes from
> getUserMedia or peerconnections.
>
> - No change. Tracks can be added to any MediaStream.
>
> Should we make a decision here?

Received on Monday, 7 October 2013 11:30:30 UTC