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

[webrtc-pc] Undefined RTCPeerConnectionState states (#2446)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Wed, 22 Jan 2020 13:16:50 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-553534697-1579699009-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-pc:

== Undefined RTCPeerConnectionState states ==
There are combinations of transport states that don't apply to any of the states in the table. For example, if all transports are "connecting" except one that is "closed", there is no corresponding RTCPeerConnectionState (because for PC/"connecting" none of the transports can be "closed" and for PC/"closed" the PC has to be closed - what if one of the transports closed due to close() or due to a close_notify alert?).

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2446 using your GitHub account
Received on Wednesday, 22 January 2020 13:16:52 UTC

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