W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: API design

From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 2 Jul 2013 05:48:00 -0700
Message-ID: <CABcZeBNBph8_wsVFWvH1PtZvL0tQiH+iODQSaU8niB-oEmk5qA@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Roman Shpount <roman@telurix.com>, "piranna@gmail.com" <piranna@gmail.com>, cowwoc <cowwoc@bbs.darktech.org>, public-webrtc <public-webrtc@w3.org>
On Fri, Jun 28, 2013 at 4:49 PM, Adam Roach <adam@nostrum.com> wrote:

> On 6/28/13 18:28, Roman Shpount wrote:
>
>> Looking at the amount of code reuse I am not sure we can count Chrome and
>> Firefox as two implementations. Maybe one and a half.
>>
>
> You're very confused on this point.
>
> The code we share in common is pretty much limited to the media processing
> (e.g. codecs), which isn't really the subject of the standardization that
> is currently underway.
>
> Firefox's implementation of the two major specs -- PeerConnection and
> getUserMedia -- is completely independent of Chrome's, as is our network
> transport (e.g., ICE and DTLS).


One clarification: Firefox and Chrome use the same DTLS stack; NSS.
However, I am familiar with non-browser implementations which use
OpenSSL's stack.

-Ekr
Received on Tuesday, 2 July 2013 12:49:11 UTC

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