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

JSEP: Check about state-changing and not-state-changing calls

From: Harald Alvestrand <harald@alvestrand.no>
Date: Mon, 02 Jan 2012 12:01:24 +0100
Message-ID: <4F018E84.7030305@alvestrand.no>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Just to be sure I understand the JSEP proposal properly:

As I understand it, the following calls cause NO change in browser state:

pc.createOffer()
pc.createAnswer()

The following calls can cause a change to the overall PeerConnection 
state (between NEW, ACTIVE and CLOSED), and may cause changes to the 
incoming media streams' states:

pc.setLocalDescription()
pc.setRemoteDescription()

The following calls cause a change to the ICE processing state, and may 
cause (delayed) changes to the incoming media streams' states, by 
letting media flow:

pc.connect()
pc.processIceMessage()

The following calls cause a change in local (outgoing) media stream 
state, but do NOT trigger any automatic renegotiation, so do NOT cause 
any state change on the remote end, but WILL affect the result of 
pc.createOffer() and pc.createAnswer() if called:

pc.addStream()
pc.removeStream()

Is this understanding correct?

                           Harald
Received on Monday, 2 January 2012 11:01:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:26 UTC