Cloning and sharing of MediaStreamTracks - worth it?

Just a quick question....

I have checked with the implementors, and the change to allow both 
cloning and copying of MediaStreamTracks is going to be quite a 
significant burden - there's quite a bit of code there that is written 
with the assumption that one MediaStreamTrack belongs to one and only 
one MediaStream, because the previous version of the API guaranteed that.

I have understood that Adam feels strongly that the design where a 
MediaStreamTrack (with its muted state, constraints and everything else) 
can be a member of multiple MediaStreams is a better design.

I just want to verify that the rest of the group shares the consensus 
(and that our partners at Mozilla are also willing to implement this 
change).

                Harald

Received on Monday, 6 May 2013 15:16:20 UTC