Re: onerror eventhandler not added to RTCRtpSender/Receiver from Bernard Aboba on 2014-05-27 (public-ortc@w3.org from May 2014)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Tue, 27 May 2014 02:45:46 +0000
To: "Anniruddh Koppal (Persistent Systems Ltd.)" <v-ankopp@microsoft.com>
CC: Bernard Aboba <Bernard.Aboba@microsoft.com>, "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <7285BF0C-20C2-41D8-BD03-28F6AB8A364F@microsoft.com>

Wouldn't that generate an exception?

On May 24, 2014, at 11:40 AM, "Anniruddh Koppal (Persistent Systems Ltd.)" <v-ankopp@microsoft.com<mailto:v-ankopp@microsoft.com>> wrote:

One case is when user tries to send/receive stream that has been stopped.



From: Bernard Aboba
Sent: Friday, May 23, 2014 7:51 PM
To: Anniruddh Koppal (Persistent Systems Ltd.); public-ortc@w3.org<mailto:public-ortc@w3.org>
Subject: RE: onerror eventhandler not added to RTCRtpSender/Receiver

What kinds of error events would occur in the Sender and Receiver (as opposed to the ICE and DTLS Transport objects)?

From: Anniruddh Koppal (Persistent Systems Ltd.) [mailto:v-ankopp@microsoft.com]
Sent: Friday, May 23, 2014 6:28 AM
To: public-ortc@w3.org<mailto:public-ortc@w3.org>
Subject: onerror eventhandler not added to RTCRtpSender/Receiver

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


Regards,
Anniruddh

Received on Tuesday, 27 May 2014 02:46:20 UTC