- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Apr 2016 08:00:09 +0000
- To: public-ortc@w3.org
murillo128 has just created a new issue for https://github.com/openpeer/ortc: == Value of onssrcconflict event in RTCRtpSender == Currently we have an onssrcconflict in the RTCRtpSender, but I fail to see which situations would cause it to be triggered. AFAIK the only way of having an ssrc conflict is by assigning the same ssrc to two different RTPSender on same transport, or having two different encodings with same ssrc. Or when changing a sender from one transport to another which already had another RTPSender using that same ssrc. This can only be triggered by an API method call (either `RTCRtpSender.send()`or RTCRtpSender.setTransport()`) so IMHO it is much better to throw an exception in this case (an InvalidParameter exception for `send()` and maybe a new SSRConflict exception for `setTranspor()`), that triggering an event. Please view or discuss this issue at https://github.com/openpeer/ortc/issues/448 using your GitHub account
Received on Friday, 1 April 2016 08:00:14 UTC