- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Wed, 17 Apr 2013 09:38:47 +0200
- To: robert@ocallahan.org
- CC: Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2013-04-17 09:30, Robert O'Callahan wrote: > The MediaStream constructor that takes a MediaStream parameter is > underspecified; the spec just says "the given stream is cloned" and does > not say whether the two streams share the underlying track set or not. I > had assumed the track sets would not be shared --- the new stream would > have a copy of the original stream's current track set, and would not be > updated as the original stream's track set changes --- but you have > assumed they will share a single underlying track set. > > Note that if the track set is shared then the spec text "separate > MediaStream instances can be manipulated and consumed individually" is > misleading since addTrack/removeTrack on one stream would affect the > other one. Are you looking at the editor's draft? [1] The constructor currently clones all tracks, but we're talking about making the cloning explicit for clarity. Regardless if we clone the tracks or not, the "track set" itself, is always a copy in the new stream. /Adam [1] http://dev.w3.org/2011/webrtc/editor/getusermedia.html#dom-mediastream [2] http://lists.w3.org/Archives/Public/public-media-capture/2013Apr/0105.html
Received on Wednesday, 17 April 2013 07:55:05 UTC