RE: Panic between createOffer() and setLocalDescription() from Matthew Kaufman (SKYPE) on 2014-02-19 (public-webrtc@w3.org from February 2014)

From: Matthew Kaufman (SKYPE) <matthew.kaufman@skype.net>
Date: Wed, 19 Feb 2014 14:01:54 +0000
To: "piranna@gmail.com" <piranna@gmail.com>, Iñaki Baz Castillo <ibc@aliax.net>
CC: public-webrtc <public-webrtc@w3.org>, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, Christer Holmberg <christer.holmberg@ericsson.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A4844AB8BE31@TK5EX14MBXC296.redmond.corp.microsoft.>

I believe what you suggest would violate the principle of least surprise.

Matthew Kaufman

From: piranna@gmail.com [mailto:piranna@gmail.com]
Sent: Wednesday, February 19, 2014 1:06 AM
To: Iñaki Baz Castillo
Cc: public-webrtc; Stefan Håkansson LK; Christer Holmberg; Silvia Pfeiffer
Subject: Re: Panic between createOffer() and setLocalDescription()


> - It forces the developer to retrieve a SDP from the PeerConnection (via createOffer) and then to pass it back again to the same PeerConnection (via setLocalDescription).
>
That's the thing I find most annoying, that it's the same PeerConnection object. Wouldn't it be possible that when calling to createOffer() and createAnswer() they call internally to setLocalDescription(), so developers only need to call it explicitly if they need to modify the SDP string? This will make easier the usage of vast mayority of use cases, and also it is a backwards compatible modificatio

Received on Wednesday, 19 February 2014 14:03:05 UTC