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

Re: Google's position on the WebRTC API

From: Rob Manson <roBman@mob-labs.com>
Date: Tue, 23 Jul 2013 17:36:24 +1000
Message-ID: <51EE3278.5080306@mob-labs.com>
To: public-webrtc@w3.org
Like I said earlier...life is full of compromise 8)

It's great to hear from Google that they agree to the re-design of the 
API and I think the point that the current API can be layered on top of 
that is key. No babies and bathwater involved here.

If we focus on just mapping out the SDP rules for the most constrained 
scope possible then finishing with the current API does sound feasible.

And the new work can certainly continue in parallel to that...and will 
probably also benefit from finishing off the constrained scope version 
of the current API.

So +1 if that's what you're proposing.

PS: I think it would be good to clearly set this expectation with web 
developers so anyone using the current version of the API knows to just 
focus on apps that fit within the new constrained scope. If they choose 
to develop outside that scope then "caveat emptor"...and feel free to 
contribute to the new API development too.


On 23/07/13 13:00, Justin Uberti wrote:
> With the compromise reached in the Unified Plan document, the group has
> resolved one of the biggest remaining controversies for WebRTC, and
> cleared the way for finishing up our current specs. Given the current
> implementation state, we think it's important to complete these docs
> within the next six months, reducing scope wherever possible to make
> this happen. We can then refocus on what's next.
> Like other implementers, we've recognized that WebRTC has evolved
> significantly since we started - the original goal of a very simple,
> interoperable API has been joined by a desire for more direct, low-level
> control. We see this as the impetus for a different approach, operating
> a level lower than the current API. Such an API would be a fresh start
> and address the concerns currently being discussed in this group, but
> should also allow the current API to be layered on top of it.
> While the idea of starting this new work is exciting, just figuring out
> what is in and out of scope will take a considerable amount of time.
> That's why we propose scoping down and completing the current work now,
> and then tackling our new challenge.
> Justin, for the Google WebRTC team
Received on Tuesday, 23 July 2013 07:36:54 UTC

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