W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2017

[webrtc-pc] "getParameters" and "setParameters" need more thorough specification

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Fri, 07 Apr 2017 04:29:32 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-220107320-1491539370-sysbot+gh@w3.org>
taylor-b has just created a new issue for https://github.com/w3c/webrtc-pc:

== "getParameters" and "setParameters" need more thorough specification ==
The description of `RTCRtpSender.getParameters`, for example, is currently just:

> The getParameters method returns the RTCRtpSender object's current parameters for how track is encoded and transmitted to a remote RTCRtpReceiver.

But it's not obvious how and when these "current parameters" are populated. My understanding, from working group discussions back when the sender/receiver APIs were first being introduced, was that `getParameters` would return nothing until a remote description is set (or a local description, for an `RTCRtpReceiver`), after which the envelope of possible parameters is determined by SDP.

`setParameters` could also be more clear about all the things that are allowed to change. We already have "read-only parameter" markings where the parameter is defined, but a short summary at the top of the `setParameters` description wouldn't hurt.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1116 using your GitHub account
Received on Friday, 7 April 2017 04:29:38 UTC

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