W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2012

Re: What is the closing state for?

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Mon, 27 Aug 2012 14:21:39 +0000
To: Eric Rescorla <ekr@rtfm.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <E9840B9A-1BB8-47E1-B78D-3749250DAA8B@cisco.com>

On Aug 24, 2012, at 8:15 AM, Eric Rescorla <ekr@rtfm.com> wrote:

> Looking over the current specification I see that it specifies a "closing" state
> for the RTCPeerStateEnum (see S 5.1.6). However, I don't see any way
> to get into that state. The specification requires that when you call pc.close()
> you transition right to the CLOSED state:
>  When the close() method is invoked, the user agent must run the
> following steps:
>  If the RTCPeerConnection object's RTCPeerConnection readiness state
> is CLOSED (3), throw an INVALID_STATE_ERR exception.
>  Destroy the RTCPeerConnection ICE Agent, abruptly ending any active
> ICE processing and any active streaming, and releasing any relevant
> resources (e.g. TURN permissions).
>  Set the object's RTCPeerConnection readiness state to CLOSED (3).
> And looking through the document I see no references to any state transition
> that would bring the PC (as opposed to the DataChannel) to CLOSING.
> I propose we remove the CLOSING state.
> -Ekr

Received on Monday, 27 August 2012 14:22:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 August 2012 14:22:33 GMT