onerror in RTCRtpReceiver and RTCRtpSender objects #95

Closed
aboba opened this Issue Jun 2, 2014 · 6 comments

Projects

None yet

2 participants

@aboba
Contributor
aboba commented Jun 2, 2014

From: Anniruddh Koppal (Persistent Systems Ltd.) v-ankopp@microsoft.com
Date: Fri, 23 May 2014 10:28:16 +0000
To: "public-ortc@w3.org" public-ortc@w3.org
URL: http://lists.w3.org/Archives/Public/public-ortc/2014May/0131.html

onerror eventhandler needs to be added to RTCRtpSender/RTCRtpReceiver objects.

@aboba
Contributor
aboba commented Jun 3, 2014

A potential resolution to this is to add onerror eventhandlers to the sender and receiver objects.

@aboba aboba closed this Jun 6, 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 aboba reopened this Jun 27, 2014
@aboba
Contributor
aboba commented Jun 27, 2014

From Shijun Sun: not clear when the “error” event should be fired on the RtpSender and RtpReceiver.

@robin-raymond robin-raymond added the 1.1 label Jun 28, 2014
@aboba
Contributor
aboba commented Jul 8, 2014

Proposed resolution: Since we don't have a use case, take it out.

@aboba
Contributor
aboba commented Jul 15, 2014

This probably will require implementation feedback. For example, some issues with RTCRtpParameters might not be addressable via exceptions.

@aboba
Contributor
aboba commented Jul 21, 2014

One potential use for onerror is to handle issues with RTCRtpParameters that don't result in an Exception being thrown.

@aboba
Contributor
aboba commented Jul 31, 2014

Add the following to the onerror description in the sender and receiver objects:

" This event MUST be fired if an issue is found with the RTCRtpParameters object passed to
send/receive that is not immediately detected."

@aboba aboba closed this Jul 31, 2014
@robin-raymond robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Aug 19, 2014
Robin Raymond Clarification of the ICE restart issue, as noted in:
w3c#93

Clarified onerror usage in sender and receiver objects, as noted in:
w3c#95

Clarified SST-MS capability issue noted in:
w3c#108

Clarification of send() and receive() usage as noted in:
w3c#119

Changed ICE state diagram as noted in:
w3c#122

Removed getParameters methods and changed send() method as noted in:
w3c#136

Changed definition of framerateScale and resolutionScale as noted in:
w3c#137

Substituted "muxId" for the "receiverId" as noted in:
w3c#138
w3c#140

Clarified the setting of track.kind as described in:
w3c#141

Added SSRC conflict event to the RTCRtpSender, as described in:
w3c#143

Addressed the "end of candidates" issues noted in:
w3c#142
w3c#144
4916cd5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment