Capabilities and Settings #84

Closed
aboba opened this Issue May 12, 2014 · 1 comment

Projects

None yet

2 participants

@aboba
Contributor
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 robin-raymond added the 1.1 label May 13, 2014
@robin-raymond robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Jun 15, 2014
Robin Raymond - Added support for non-multiplexed RTP/RTCP and ICE freezing, as des…
…cribed in Issue 57


w3c#57

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

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

- Partially addressed capabilities issues, as described in Issue 84
w3c#84

Addressed WebIDL type issues described in Issue 88
w3c#88

- Addressed Overview section issues described in Issue 91
w3c#91

- Address readonly attribute issues described in Issue 92
w3c#92

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

- Added onerror eventhandler to sender and receiver objects as described in Issue 95
w3c#95
f74b889
@aboba
Contributor
aboba commented Jun 15, 2014

Capabilities and Settings from getUserMedia have been removed in the latest editor's draft:
http://ortc.org/wp-content/uploads/2014/06/ortc.html

@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