- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jul 2020 13:57:14 +0000
- To: public-webrtc-logs@w3.org
BTW example 2) of changing bundlePolicy is not possible due to > If the value of configuration.bundlePolicy is set and its value differs from the connection's bundle policy, throw an InvalidModificationError. However stopping a transceiver may or may not stop the transport depending on bundle policy and number of m= sections. I suggest delaying stopping the transport until the O/A exchange for a few reasons... - Until O/A happens, we don't know if there will be any other transceivers that want to reuse this transport or m= section. - Telling the other endpoint that the transport is about to stop seems more graceful. - Transports are already configured by JSEP, so letting O/A handle this means we don't need new hooks to trigger when performing stop. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2486#issuecomment-655537225 using your GitHub account
Received on Wednesday, 8 July 2020 13:57:15 UTC