- From: westhawk <thp@westhawk.co.uk>
- Date: Wed, 19 Jul 2017 17:00:27 +0200
- To: Adam Roach <adam@nostrum.com>
- Cc: Iñaki Baz Castillo <ibc@aliax.net>, "public-webrtc@w3.org" <public-webrtc@w3.org>
> On 19 Jul 2017, at 14:15, Adam Roach <adam@nostrum.com> wrote: > > On 7/19/17 14:12, Iñaki Baz Castillo wrote: >> I wonder why do we need >> the "createOffer" + "setLocalDescription" ceremony at all? I mean, if >> the SDP provided by createOffer() should not be changed in any way and >> setLocalDescription() should be called with it, why does it even >> exist? It provides nothing. > > > While I might be able to come up with a reasonable-sounding explanation here (and it might even be true), the top-line practical consideration here is that we can't really make radical changes to the API flow with so much deployed code. > > /a > > At present a dummy ‘createOffer’ (not followed by setLocal) is the only way to find out the fingerprint of the certificate that would be used. We use that fact. T.
Received on Wednesday, 19 July 2017 15:00:56 UTC