W3C home > Mailing lists > Public > public-ortc@w3.org > September 2016

[ortc] sender/receiver.setTransport(): Cannot replace stop'd transport?

From: aboba via GitHub <sysbot+gh@w3.org>
Date: Fri, 09 Sep 2016 02:39:32 +0000
To: public-ortc@w3.org
Message-ID: <issues.opened-175913631-1473388770-sysbot+gh@w3.org>
aboba has just created a new issue for https://github.com/w3c/ortc:

== sender/receiver.setTransport(): Cannot replace stop'd transport? ==
Section 5.3 (sender.setTransport) and Section 6.3 
(receiver.setTransport) both contain the following sentence:

"If stop() has been called, or transport.state or rtcpTransport.state 
is closed, throw an InvalidStateError exception."

Why is it not possible for setTransport to replace an RTP or RTCP 
transport in the "closed" state? 

Please view or discuss this issue at 
https://github.com/w3c/ortc/issues/591 using your GitHub account
Received on Friday, 9 September 2016 02:39:41 UTC

This archive was generated by hypermail 2.3.1 : Friday, 9 September 2016 02:39:42 UTC