- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Feb 2018 18:43:33 +0000
- To: public-webrtc-logs@w3.org
Why should the stream association be tied to the (local) transceiver? The fact that if you're using replaceTrack, you're having odd effects on the stream associations is the biggest reason why using replaceTrack() together with streams is going to be a headache. The WG accepted that in the name of making replaceTrack() possible without a negotiation cycle. If you let removeTrack() remove the track and clear the streams list, you let addTrack/removeTrack-based applications continue to behave consistently, and make it easy to shim addStream/removeStream on top of them - in fact perfectly in the case of "one track is added only as part of one stream". removeTrack() triggers a negotiation cycle. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1756#issuecomment-362362400 using your GitHub account
Received on Thursday, 1 February 2018 18:43:38 UTC