- From: W3C Community Development Team <team-community-process@w3.org>
- Date: Fri, 6 May 2016 22:23:37 +0000
- To: public-ortc@w3.org
Updated ORTC CG Draft Report / API: http://ortc.org/wp-content/uploads/2016/05/ortc.html B.1 Changes since 01 March 2016 Added the gather() method, as noted in: Issue 165 Removed "public" from RTCIceGatherPolicy, as noted in: Issue 224 Removed the minQuality attribute, as noted in: Issue 351 Made send() and receive() asynchronous, as noted in: Issue 399, Issue 463, Issue 468 and Issue 469 Provided additional information on ICE candidate errors, as noted in: Issue 402 Added state attribute to RTCSctpTransport, as noted in: Issue 403 Provided an example of RTX/RED/FEC configuration, as noted in: Issue 404 Clarified payloadType uniqueness, as noted in: Issue 405 Updated the list of header extensions, as noted in: Issue 409 Added "goog-remb" to the list of feedback mechanisms, as noted in: Issue 410 Added kind argument to the RTCRtpReceiver constructor, as noted in: Issue 411 Clarified send() restrictions on kind, as noted in: Issue 414 Added getAlgorithm() method, as noted in: Issue 427 Changed RTCDataChannel protocol and label to USVString, as noted in: Issue 429 Clarified nullable attributes and methods returning empty lists, as noted in: Issue 433 Clarified support for the "direction" parameter, as noted in: Issue 442 Clarified the apt capability of the "red" codec, as noted in: Issue 444 Clarified usage of RTCRtpEncodingParameters attributes, as noted in: Issue 445 Clarified firing of onssrcconflict event, as noted in: Issue 448 Clarified that CNAME is only set on an RTCRtpSender, as noted in: Issue 450 Updated references, as noted in: Issue 457 Described behavior of send() and receive() with unset RTCRtpEncodingParameters, as noted in: Issue 461 Corrected dictionary initialization in the examples, noted in: Issue 464 and Issue 465 Corrected use of enums in the examples, noted in: Issue 466 Clarified handling of identity constraints, as noted in: Issue 467 and Issue 468 Clarified use of RTCRtpEncodingParameters, as noted in: Issue 470 Changed hostCandidate type, as noted in: Issue 474 Renamed state change event handlers to onstatechange, as noted in: Issue 475 Updated description of RTCIceGatherer closed state, as noted in: Issue 476 Updated description of RTCIceTransport object, as noted in: Issue 477 Updated description of relatedPort, as noted in: Issue 484 Updated description of RTCIceParameters, as noted in: Issue 485 Clarified exceptions in RTCDataChannel construction, as noted in: Issue 492 Provided a reference to error.message, as noted in: Issue 495 Clarified RTCRtpReceiver description, as noted in: Issue 496 Clarified default for clockRate attribute, as noted in: Issue 500 Removed use of "null if unset", as noted in: Issue 503 Updated RTCSctpTransport constructor, as noted in: Issue 504 Clarified behavior of getCapabilities(), as noted in: Issue 509 Addressed issues with RTCDataChannelParameters, as noted in: Issue 519 ---------- This post sent on ORTC (Object Real-time Communications) Community Group 'ORTC Draft Report Update' https://www.w3.org/community/ortc/2016/05/06/ortc-draft-report-update/ Learn more about the ORTC (Object Real-time Communications) Community Group: https://www.w3.org/community/ortc
Received on Friday, 6 May 2016 22:25:32 UTC