- From: Cullen Jennings <fluffy@cisco.com>
- Date: Tue, 4 Oct 2011 12:36:01 -0600
- To: Neil Stratford <nstratford@voxeo.com>
- Cc: public-webrtc@w3.org
Neil, what's your initial thoughts for what the API for VP8 and H.264 codec would look like in this. I think that is where stuff got hard for me when trying to sort out draft-jennings-rtcweb-api? Perhaps we can talk about this on the call tomorrow. On Sep 28, 2011, at 8:56 AM, Neil Stratford wrote: > To provide input to the ongoing discussion around architecture and inclusion/exclusion of SDP in the Javascript API we would like to put forward the following proposal. The proposal is in Google doc form for now because our goal was to get this to the list as quickly as possible, but we are happy to re-structure as a full W3C proposal or editor’s draft if required. > > https://docs.google.com/document/pub?id=1MfrFHKx6O6yWtIv_jqwyH-RAbm8AgRtXQ7dJTZz5J2g > > This API is based on an evolution of the low level media plugin API currently used by Phono and Phono Mobile. > > In Phono we have attempted to implement as much as possible in Javascript, leaving the minimum functionality that is required for either performance, device access or security to be implemented natively in browser media plugins. Signaling and codec negotiation are implemented fully in Javascript, communicating through a minimal media plugin API that exposes devices, codecs and RTP endpoints. We have existing implementations for Flash, Java applet, iOS and Android using this approach. > > For flexibility we separate RTP/ICE candidate information from codec information enabling the Javascript application the choice of implementing SDP if required. We believe that this low level API provides the ability to build a variety of signalling mechanisms, either directly in Javascript, or through the help of a bridging gateway. > > Neil Stratford > Voxeo > >
Received on Tuesday, 4 October 2011 18:36:31 UTC