W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2018

Re: [webrtc-pc] Is close() supposed to fire state change events? Connection state change set asynchronously?

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Tue, 05 Jun 2018 15:41:58 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-394758556-1528213316-sysbot+gh@w3.org>
> signaling state is set synchronously.

Signaling state is set in SLD/SRD and tracks the state of those methods essentially. We fire lots of events synchronously in those methods before the promise resolves, so I think we need to continue doing so to maintain invariants. I filed https://github.com/w3c/webrtc-pc/issues/1885 to adjust the ordering slightly.

The other two are ICE agent dependent, so having them be asynchronous makes sense to me.

> it is not clear that these steps should be executed when the ICE agent is destroyed.

I interpret the words "destroy" and "abrupt" in  _"Destroy connection's ICE Agent, abruptly ending any active ICE processing and releasing any relevant resources"_, to mean we should explicitly not perform any ordered tear-down algorithm or fire any events.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1883#issuecomment-394758556 using your GitHub account
Received on Tuesday, 5 June 2018 15:42:01 UTC

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