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

Error Handling #75

Closed
aboba opened this Issue May 2, 2014 · 0 comments

Comments

Projects
None yet
2 participants
@aboba
Copy link
Contributor

aboba commented May 2, 2014

From Shijun Sun:

  1. You need to describe the circumstances under which error events will occur. Examples include DTLS transport and ICE transport.

  2. The “onerror” interface is not defined correctly. There is no need of custom event here.

  3. Same on the “onstatechange” and some other events. If custom event is needed, the spec can say, “Fire a trust event with the name statechange, that does not bubble and is not cancelable, that uses the StateChangedEvent interface.”

     interface StateChangedEvent: Event {
       readonly attribute RTCDtlsTransportState state;
     };
    
  4. getStats, RTCErrorCallback/failureCallback is not defined or used anywhere.

@robin-raymond robin-raymond added the 1.1 label May 2, 2014

robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue May 14, 2014

Robin Raymond
- ICE restart explanation added, as described in Issue 59
w3c#59

-Fixes for error handling, as described in Issue 75
w3c#75

- Fixes for miscellaneous NITs, as described in Issue 76
w3c#76

- Enable retrieval of the SSRC to be used by RTCP, as described in Issue 77
w3c#77

- Support for retrieval of audio and video capabilities, as described in Issue 81
w3c#81

- getStats interface updated, as described in Issue 82
w3c#82

- Partially addressed SVC issues described in Issue 83
w3c#83

- Partially addressed statistics update issues described in Issue 85
w3c#85
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment