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

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

From: Justin Uberti <juberti@google.com>
Date: Tue, 3 Jan 2012 22:16:34 -0500
Message-ID: <CAOJ7v-3VwQDgHRyzLUBgW2zMdTSC9rdc0FTkK1-U7AkcB4YpuQ@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Mon, Jan 2, 2012 at 6:01 AM, Harald Alvestrand <harald@alvestrand.no>wrote:

> 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()
>

To be pedantic, CLOSED only results from a close() call.

>
> 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?
>
>
Yes, exactly.
Received on Wednesday, 4 January 2012 03:17:22 UTC

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