W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2019

[webrtc-pc] Define what happens when you stop() an offerer tagged bundled transceiver (#2049)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 10 Jan 2019 12:59:34 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-397819782-1547125173-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-pc:

== Define what happens when you stop() an offerer tagged bundled transceiver ==
At TPAC [we said](https://docs.google.com/presentation/d/1uZUmLe62faePYC2HMI_x_ltDjn_peJG71yk_PZn4hzc/edit#slide=id.g3f620ec388_2_11) to:

- Add note explaining the potential side-effects of transceiver.stop().
- Recommend that transceiver.stop() only be called on all bundled transceivers.

It is not clear from this what the side-effects should be, but it [should probably](https://github.com/w3c/webrtc-pc/pull/2001/files#r237533741) be to stop all offerer tagged bundled transceivers if we are in the signaling state "have-remote-offer". Otherwise we would have to stop the transceivers upon applying the local answer or throw an exception not to stop it in the first place.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2049 using your GitHub account
Received on Thursday, 10 January 2019 12:59:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:54 UTC