- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Fri, 17 Jan 2014 07:44:03 +0100
- To: public-webrtc@w3.org
- Message-ID: <52D8D133.4060309@alvestrand.no>
On 01/17/2014 05:55 AM, cowwoc wrote: > Hi Justin, > > This isn't strictly tied to the spec, but I think it makes a lot of > sense to release a Native API at the same time as v1 that implements > the same functionality as the Javascript API. That's out of scope for the standardization activity, however. Exactly who do you think would be interested in releasing such a thing? > > Browser peers will use the Javascript API while non-browser peers > (mobile native apps, servers and gateways) will use the Native API. > Currently everyone is rolling out their own version and there is a > huge amount of wasted effort reinventing the wheel. > > So to reiterate: the purpose of this API isn't code portability, but > rather it is meant to be a reference/sample implementation of the > functionality. Right now some of this functionality resides in Chrome > (sitting above the Native API). Essentially I'm just asking you to > move as much WebRTC-specific functionality out of Chrome and into the > Native API such that (as much as possible) the Javascript API is a > thin layer on top of native code.
Received on Friday, 17 January 2014 06:44:31 UTC