Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTCRtpCodecCapability options vs parameters #412

Closed
ibc opened this issue Mar 11, 2016 · 4 comments
Closed

RTCRtpCodecCapability options vs parameters #412

ibc opened this issue Mar 11, 2016 · 4 comments

Comments

@ibc
Copy link
Contributor

ibc commented Mar 11, 2016

RTCRtpCodecCapability

options of type Dictionary

Codec-specific parameters available for signaling.

parameters of type Dictionary

Codec-specific parameters that must be signaled to the remote party.

Honestly, no idea which the difference is :)

@robin-raymond
Copy link
Contributor

parameters are those things that the remote party must know about where as options are either optional parameters to be sent to the remote party or other local/informational options for a particular codec (but the remote party need not know about it).

@robin-raymond
Copy link
Contributor

@ibc can I close down this question issue now?

@ibc
Copy link
Contributor Author

ibc commented Apr 16, 2016

Sure, if the spec clearly describes the above explanation (I've not checked the text regarding it in master).

@robin-raymond
Copy link
Contributor

Hmm... I don't think the spec is clear enough. I think we need need a tweak:

We should likely change:

options of type Dictionary
Codec-specific parameters available for signaling.

To:

options of type Dictionary
Codec-specific parameters that may be optionally signalled and are available as additional supported information or settings about the codec.

... or something like that...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants