- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Thu, 25 Jan 2018 13:34:32 +0100
- 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 <ibc@aliax.net>
Received on Thursday, 25 January 2018 12:35:16 UTC