New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SctpTransport has no state or state change event #403

Closed
aboba opened this Issue Mar 1, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@aboba
Contributor

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

This comment has been minimized.

Show comment
Hide comment
@aboba

aboba Mar 12, 2016

Contributor

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

Contributor

aboba commented Mar 12, 2016

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

@robin-raymond

This comment has been minimized.

Show comment
Hide comment
@robin-raymond

robin-raymond Mar 13, 2016

Contributor

@aboba Yes.

Contributor

robin-raymond commented Mar 13, 2016

@aboba Yes.

@aboba

This comment has been minimized.

Show comment
Hide comment
@aboba

aboba Mar 15, 2016

Contributor

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.

Contributor

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 added a commit that referenced this issue Mar 15, 2016

@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