Re: non-normative sections using RTCSessionDescription

I see, message.sdp is an RTCSessionDescription object (which in turn has a
sdp key). I think what confused me is that there is essentially an object
named sdp with an sdp key.

Paul


On Thu, Feb 13, 2014 at 12:01 AM, Adam Bergkvist <
adam.bergkvist@ericsson.com> wrote:

> On 2014-02-06 01:17, Paul Ellenbogen wrote:
>
>> The specification defines the constructor of RTCSessionDescription
>> <http://www.w3.org/TR/webrtc/#rtcsessiondescription-class> as taking a
>>
>> single RTCSessionDescriptionInit dictionary object as an argument. The
>> dictionary has the keys "type" and "sdp".
>>
>> In two of the non-normative sections which create RTCSessionDescription
>> objects, a single "sdp" string is passed as an argument. Example 4 in
>> section 13.1 <http://www.w3.org/TR/webrtc/#simple-peer-to-peer-example>
>>
>> does this. Example 6 in section 13.3
>> <http://www.w3.org/TR/webrtc/#peer-to-peer-data-example> does this.
>>
>>
>> It seems like these sections should be updated to reflect the changes to
>> RTCSessionDescription constructor specification.
>>
>
> Hi
>
> Thanks for reviewing the spec.
>
> message.sdp is actually an object since message is the result of doing
> JSON.parse() on evt.data.
>
> From example:
> var message = JSON.parse(evt.data);
> if (message.sdp)
>   pc.setRemoteDescription(new RTCSessionDescription(message.sdp), ...
>
> /Adam
>