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

Re: Raw data API - 4 - direct RTP access

From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Wed, 30 May 2018 21:06:57 +0200
To: Peter Thatcher <pthatcher@google.com>
Cc: public-webrtc@w3.org
Message-ID: <6230cb4c-73d8-9a34-f6f6-5bda72f2cf9b@gmail.com>
On 30/05/2018 20:06, Peter Thatcher wrote:
> What objection do you have in these things being provided by libraries 
> instead of being baked in the browser?

Availability, interoperability, browser compatibility, fragmentation and 
in a lower degree, support and low end devices performance.

You take it for granted that someone will spend time and resources to 
create a library to provide a higher level api, deal with the browser 
differences and provide a good enough api to be used by everyone else. 
This is quite unlikely, specially if QUIC is supposed to provide the 
same functionality with a well defined, documented, tested and supported 
api on browsers from day 0.

Big players will likely, if they decide to go for QUIC over RTP, 
implement their own libs, doing custom things, and media server people 
will have hard time implementing all kind of custom rtx and fec 
implementations to try to be compatible, or having to implement their 
own js stacks to be compatible with their own media servers. This will 
create silos and fragment the market, making it very difficult for 
small/medium open source media servers projects to survive (or forced to 
migrate to QUIC).

Best regards

Received on Wednesday, 30 May 2018 19:06:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:41 UTC