W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2018

Re: What would you like to see in WebRTC next? A low-level API?

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 25 Jan 2018 13:34:32 +0100
Message-ID: <CALiegfmcNjT7b3opvPWfDdYuML3gF5T6++FaB0r4cbjY_nSXEA@mail.gmail.com>
To: Philipp Hancke <fippo@goodadvice.pages.de>
Cc: public-webrtc@w3.org
On 25 January 2018 at 13:25, Philipp Hancke <fippo@goodadvice.pages.de> wrote:
> The approach to treat SDP as an "opaque blob" simply did not work. Yes, that
> means that there is a lot of stuff in the API that is showing how SDP O/A
> works, in particular the transceiver. It also means that there is no way
> RTCPeerConnection can get rid of SDP now.

errrr, honestly, I don't want a "RTCPeerConnection" or
"RTCPeerConnectionNG" in next WebRTC API.

>> If we really want to make WebRTC useful for developers other than
>> browser vendors and C++ experts, we cannot transmit a SDP blob as the
>> "minimum irreducible unit for exchanging multimedia information".
> Having a committee (consisting mostly of RTC folks) design a Javascript API
> is going to be... well, see that chrome devrel tweet ;-)

A committee that years ago decided that passing a SDP blob was a good
API? Yes, probably we need different profiles in the room.

Iñaki Baz Castillo
Received on Thursday, 25 January 2018 12:35:16 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 January 2018 12:35:16 UTC