Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)

[Iñaki Baz Castillo <[e-mail]>]

2011/10/5 Tim Panton <[e-mail]>:
> On 5 Oct 2011, at 10:19, Iñaki Baz Castillo wrote:
>
> - Now please generate my SDP as a reply for the received SDP:
>
>  var my_sdp = WebRTC.SDP.answerFor(remote_sdp);
>
> - ...but discard the video offered by the peer.
>
>  my_sdp.removeStream("video");
>
> It seems to me that by calling WebRTC.SDP.answerFor() - getting the native
> code
> to do the 'compatibility matching' you've lost quite a lot of influence over
> the selection process.
> Lets say this is a conference app on an android phone - and lets say that
> the phone supports
> h 261, h263 and h264 but only has hardware accel for h264 - the app's screen
> layout is such that
> we only want a postage stamp of the remote user and a still image would be
> preferable to a
> poorly rendered moving one (less distracting) . (so I'd like h264 or
> nothing)
>
> How does the app express that set of preferences in your scenario?
> If the app gets all the capabilities data as JSON objects, it can make
> decisions itself,
> eliminating the ones that don't fit the usecase even though they do actually
> 'match'.
> That's why I'd like to see the matching and elimination done in javascript,
> with the data
> presented in a JS friendly manner. It can then be converted to SDP for
> sending over the
> (web-socket) wire if needed.


Hi Tim, honestly I didn't expect to define the full WebRTC JS API in 5
minutes while I was writting the mail :)

Your points are perfectly valid and should indeed be covered. But I
didn't want to be so explicit in my immature API suggestion. It was
just an overview.

Regards.

-- 
Iñaki Baz Castillo
<[e-mail]>