W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2012

Re: Code examples: Existing API and JSEP

From: Cullen Jennings <fluffy@cisco.com>
Date: Fri, 27 Jan 2012 09:19:40 -0700
Cc: Adam Bergkvist <adam.bergkvist@ericsson.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-Id: <90485D9B-A59A-4644-AF4A-CEAD48844213@cisco.com>
To: Justin Uberti <juberti@google.com>

On Jan 26, 2012, at 9:24 PM, Justin Uberti wrote:

>> 
>> - Special cases such as glare and multiple offers have to be handled in
>> JavaScript.
>> A simple example with the existing API (and ROAP) is quite powerful sice
>> special
>> cases are handled under the hood.
>> 
> 
> Right, this is what we acknowledged as a tradeoff of JSEP; by pushing more
> control into JS, more code is needed. But as you can see, the amount of
> code is not that large, and this could easily be placed into a JS library.

Uh, I think the coded needed is a lot more than this and I am still waiting for an answer on what it is that you can do with JSEP's "more control"

> 
>> 
>> It's also a question if PeerConnection.createOffer() and
>> PeerConnection.createAnswer()
>> actually can have a return value? If the browser needs to reach down into
>> the platform
>> to gather information these methods may need to be async and use a
>> callback.
>> 
> 
> Good point. I'd be interested in knowing whether anyone would need this.

Yes - if you were implementing video on something like a iPhone, you would. 
Received on Friday, 27 January 2012 16:20:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:27 UTC