W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2017

Re: [webrtc-pc] End removed tracks remotely again; Make receiver.track nullable instead

From: stefan hakansson via GitHub <sysbot+gh@w3.org>
Date: Thu, 11 May 2017 08:27:28 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-300719460-1494491247-sysbot+gh@w3.org>
I think it would be good to work through the events (in terms of `pc.removeTrack`, `transceiver.setDirection` and so on, assuming `onnegotiationneeded` is wired up) that would lead to "send" and "recv" bits being set/unset.

But overall this looks like something that could work. If the intent is to have the received track being constantly played or recorded, the sender can play with `replaceTrack` and use a null track for periods when there is nothing to send.

GitHub Notification of comment by stefhak
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1181#issuecomment-300719460 using your GitHub account
Received on Thursday, 11 May 2017 08:27:34 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:40 UTC