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

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

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 10 Oct 2013 05:25:36 +0200
Message-ID: <52561E30.9080708@alvestrand.no>
To: Adam Bergkvist <adam.bergkvist@ericsson.com>
CC: public-media-capture@w3.org
On 10/07/2013 01:30 PM, Adam Bergkvist wrote:
> 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.

This change is not strictly backwards compatible, in that some code that
works today will break under the new specification.

But the nice thing about it is that it's forward compatible - if we
decide to relax the restriction, no code should need to change.
Received on Thursday, 10 October 2013 03:26:05 UTC

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