W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2014

Re: Panic between createOffer() and setLocalDescription()

From: <piranna@gmail.com>
Date: Mon, 10 Mar 2014 08:47:36 +0100
Message-ID: <CAKfGGh3UsByF9vu3ShqE4JWzSc+HfK_Ox6vMaHxu-uH0nLutHg@mail.gmail.com>
To: Kiran Kumar <g.kiranreddy4u@gmail.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, public-webrtc <public-webrtc@w3.org>
> Setting sdpMangling to false (which is case for majority of
scenarios/apps) will speedup the process, because browser can start
processing the sdp without waiting for setLocalDescription.
I agree with you in that's the way to go, but there's another issue:
trickle ICE. Without the hability to disable it, the offer description on
createOffer/createAnswer is fairly useless by don't having candidates. And
yes, needing to wait for externally dispatched candidate events is
counter-intuitive, after all this time dealing with WebRTC I still forget
them when creating new code code from scratch. Trickle ICE should be an
advanced functionality behind a flag (the same as your proposed sdpMangling
flag) instead of a by default feature if we really want WebRTC to be easy
to use by newcomers. I think this will greatly help to increase WebRTC
adoption that releasing a 1.0 spec soon, and it's a thing that will not
delay it beyond than one release more.
Received on Monday, 10 March 2014 07:48:04 UTC

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