W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2014

Re: non-normative sections using RTCSessionDescription

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Thu, 13 Feb 2014 09:01:35 +0100
Message-ID: <52FC7BDF.6090903@ericsson.com>
To: Paul Ellenbogen <epaul9@cs.washington.edu>, <public-webrtc@w3.org>
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
Received on Thursday, 13 February 2014 08:01:59 UTC

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