- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Feb 2018 18:13:58 +0000
- To: public-webrtc-logs@w3.org
@fippo It shouldn't, because the stream association is still tied to the transceiver. E.g. If I then do ```js await sender.replaceTrack(trackB); sender.direction = "sendrecv"; ``` Then remotely (after renegotiation) the receiver.track would again pop up in the same-id remote stream. Confused? See https://github.com/w3c/webrtc-pc/issues/1758 which I just filed. What I think is true however, is that we probably don't need to keep a reference to the streams themselves, just their ids. Since keeping a stream open has side-effects (local camera staying on) that seems like an improvement (remember what's being sent may come from an entirely different stream). -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1756#issuecomment-362353997 using your GitHub account
Received on Thursday, 1 February 2018 18:14:02 UTC