18486 2012-08-04 00:22:02 +0000 Let RTCSessionDescription take a Dictionary parameter 2012-09-13 14:49:59 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified PC Linux RESOLVED FIXED P2 normal --- 1 harald adam.bergkvist adam.bergkvist public-webrtc tommyw oldest_to_newest 71838 0 harald 2012-08-04 00:22:02 +0000 From Tommy Widenflycht, July 31 (see mailing list for discussion): Today I would like to propose a small change to RTCSessionDescription and RTCIceCandidate which would make the much more flexible: [Constructor(optional Dictionary description)] interface RTCSessionDescription { attribute RTCSdpType type; attribute DOMString sdp; }; In short the single constructor takes an Dictionary which is expected to mimic its members, and the stringifier method is removed. This has the advantages of being extremely powerful: sd = new RTCSessionDescription(); sd.sdp = ...; sd.type = ...; sd = new RTCSessionDescription({sdp:"..."}); sd.type = ...; sd = new RTCSessionDescription({type:"answer", sdp:"..."}); sd = new RTCSessionDescription(JSON.parse(some_json_string)); sd2 = new RTCSessionDescription(sd); and in the other direction jsonified_sd = JSON.stringify(sd); There's some precedence in using a constructor like this in some of the base Event classes. 72113 1 adam.bergkvist 2012-08-13 09:29:59 +0000 It's nice that the constructor takes an object rather than a string of JSON. I'll go ahead and add this to the spec. I'm not sure this cloning functionality works though: > sd2 = new RTCSessionDescription(sd);