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

Capabilities and Settings #84

aboba opened this issue May 12, 2014 · 1 comment

Capabilities and Settings #84

aboba opened this issue May 12, 2014 · 1 comment


Copy link

@aboba aboba commented May 12, 2014

From Shijun Sun:

Based on the spec, Capabilities and Settings are defined as “dictionary containing one or more key-value pairs.”

There are 5 of them in the ORTC spec so far.

Capabilities features;
Capabilities rtcpFeedback;

Capabilities formats;

Settings formats;
Settings rtcpFeedback;

A couple observations:

  1.  Some should probably be defined as “sequence” of something.  IMHO we should avoid the “Capabilities” stuff if it is not needed.
  2.  I expect that Capabilities” and “Settings” are always in pairs.  So far, there is no “features” Settings, only the “features” Capabilities.
robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Jun 15, 2014
…cribed in Issue 57


- Added support for getRemoteCertificates(), as described in Issue 67

- Removed filterParameters and createParameters functions, as described in Issue 80

- Partially addressed capabilities issues, as described in Issue 84

Addressed WebIDL type issues described in Issue 88

- Addressed Overview section issues described in Issue 91

- Address readonly attribute issues described in Issue 92

- Added ICE restart method to address the issue described in Issue 93

- Added onerror eventhandler to sender and receiver objects as described in Issue 95
Copy link
Contributor Author

@aboba aboba commented Jun 15, 2014

Capabilities and Settings from getUserMedia have been removed in the latest editor's draft:

@aboba aboba closed this Jun 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants