SctpTransport has no state or state change event #403

aboba opened this Issue Mar 1, 2016 · 3 comments


None yet

2 participants

aboba commented Mar 1, 2016

If the remote side calls stop() on the SctpTransport the local SctpTransport will be closed. How does the developer know this has happened?

@aboba aboba added the 1.1 label Mar 1, 2016
aboba commented Mar 12, 2016

If the remote SctpTransport is closed, RTCDataChannelState will transition to "closed" and the RTCDataChannel "onclosed" event handler will fire.

@aboba aboba added the 1.0 label Mar 12, 2016

@aboba Yes.

@aboba aboba removed the 1.0 label Mar 15, 2016
aboba commented Mar 15, 2016

What happens if an RTCDataChannel has not been constructed yet and sctpTransport.stop() is called? In that case, we will indeed need SctpTransport.state and a state change event. Ugh.

@aboba aboba added a commit that referenced this issue Mar 15, 2016
@aboba aboba SctpTransport state and state change event
Fix for Issue #403
@aboba aboba added the PR exists label Mar 15, 2016
@aboba aboba closed this Mar 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment