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]>:
>> 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.


> I guess what I was getting at was the fact that the SDP seemed
> central to the API - I'd like something more generic and javascript
> friendly as the central concept.


Hi Tim. At the end you web application will receive (via the custom
signaling) something "like" and SDP containing the media information
offered/answered by the peer (when receiving or initiating a media
session).

This is: your web browser needs to know the remote IP:port, the media
streams, supported codecs by the peer... At the end that looks like a
SDP. And such "SDP" should be retrieved by your web application via
some signaling protocol (on top of HTTP or WebSocket), and you will
receive it as a JSON object, or XML, or whatever format.

Then you will always need to parse such "like-SDP", obtain something
like a WebRTC.SDP object, and use it for starting/answering a session.

You can propose a different name, something like...
"WebRTC.SessionDescription"? :)
but the underlying concept is the same (IMHO).

Regards.


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