If SDP-backers really want to ship WebRTC 1.0 as soon as possible, then either mandate that SDP may not be mangled at all (in which case they need to add API methods for use-cases that currently require SDP mangling) or explicitly state that SDP mangling will result in "undefined behavior". The more SDP-related crap we add into the API, the harder it will be to remove it in 2.0. Gili On 10/03/2014 5:33 AM, Iñaki Baz Castillo wrote: > 2014-03-10 8:15 GMT+01:00 Kiran Kumar <g.kiranreddy4u@gmail.com>: > >> 1.2) If sdpMangling is set to true, then UA should be provided with a list of parameters/attributes that he is allowed to modify. > I disagree. Such a list of modifiable parameters/attributes should be > given by the specification, no by each browser. > > >> 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. > The elapsed time between createOffer() and setLocalDescription() is > about a few nanoseconds (in the worst case). Completely irrelevant > having later to perform ICE procedures (gathering and path > negotiation). > >Received on Monday, 10 March 2014 16:25:47 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:55 UTC