- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Sep 2020 07:48:08 +0000
- To: public-webrtc-logs@w3.org
So, what about removing the unassociated transceiver as soon as stop is called? "If it doesn't have a mid, kill it quickly." Arguments against this: - More edge cases makes the API unpredictable. - Not clear if there is a valid use case. Arguments for this and possible use case: - I create a transceiver for sending, but before I have a chance to negotiate this I get a remote offer that creates a sendrecv transceiver. Realizing I no longer need my transceiver, I stop it, and I complete the negotiation process. If the transceiver was instantly removed, there wouldn't be a pointless follow-up offer. If the transceiver wasn't removed, I'd have to do a follow-up O/A exchange that says "here's an inactive and stopped m= section for you, there you go" -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2576#issuecomment-696563705 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 September 2020 07:48:11 UTC