[ortc] receiver.setTransport(...) and then killing transport different than receiver.setTransport(null)?

• From: Robin Raymond via GitHub <sysbot+gh@w3.org>
• Date: Mon, 15 Jan 2018 19:51:02 +0000
• To: public-ortc@w3.org
• Message-ID: <issues.opened-288699887-1516045861-sysbot+gh@w3.org>

robin-raymond has just created a new issue for https://github.com/w3c/ortc:

== receiver.setTransport(...) and then killing transport different than receiver.setTransport(null)? ==
If  it's possible to call receiver.setTransport(aTransport) and then call aTransport.stop(). Why would it be any different to handle this case vs allowing receiver.setTransport(null) to remove the transport rather than keeping a live receiver attached to a dead transport.

Please view or discuss this issue at https://github.com/w3c/ortc/issues/804 using your GitHub account

Received on Monday, 15 January 2018 19:51:03 UTC