Mandatory "kind" in RTCRtpReceiver constructor

[aboba]

Should the "kind" argument be mandatory (not optional) in RTCRtpReceiver?

[aboba]

If done, the interface would look like this:

[Constructor(DOMString kind, RTCDtlsTransport transport, optional RTCDtlsTransport rtcpTransport)]
partial interface RTCRtpReceiver : RTCStatsProvider {
readonly attribute MediaStreamTrack track;
};

Not that "readonly attribute MediaStreamTrack track" is also used in the WebRTC 1.0 RTCRtpReceiver definition.

[pthatcherg]

What would be the advantage of supplying it?

On Mon, Aug 4, 2014 at 9:12 PM, aboba notifications@github.com wrote:

If done, the interface would look like this:

[Constructor(DOMString kind, RTCDtlsTransport transport, optional
RTCDtlsTransport rtcpTransport)]
partial interface RTCRtpReceiver : RTCStatsProvider {
readonly attribute MediaStreamTrack track;
};

Not that "readonly attribute MediaStreamTrack track" is also used in the
WebRTC 1.0 RTCRtpReceiver definition.

—
Reply to this email directly or view it on GitHub
#141 (comment).

[aboba]

Here is a proposed resolution:

In Section 9.7.1, add the following text to the explanation of RTCRtpCodecParameters.name:
The name MUST always be provided.

In Section 7.3.2, add the following explanatory text to "receive":

After receive() returns, track is set, and the value of track.kind is determined based on the kind of the codecs provided in parameters.codecs. If all the codecs are of a single kind then track.kind is set to that kind; if the kind differs between codecs, then track.kind is set to "all".

[aboba]

Oops, should be "", not "all".

[pthatcherg]

Sounds good to me.

On Wed, Aug 6, 2014 at 10:38 AM, aboba notifications@github.com wrote:

Oops, should be "", not "all".

—
Reply to this email directly or view it on GitHub
#141 (comment).