The connection status has failed,Why is the read function still blocking?

[xdeng]

Your environment.

• Version: v4.0.0-beta.29
• Browser:
• Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context

What did you do?

data-channels-detach

What did you expect?

What happened?

The connection status is

OnConnectionStateChange: disconnected
OnConnectionStateChange: failed

dataChannel.Detach() ---> ReadWriteCloser, Why doesn't it fail when reading, but keeps blocking?

Need to call peerConnection.Close(), The read function will fail to exit.

[xdeng]

I would also like to ask how to implement timeout for the separated read-write close functions? Or context

[xdeng]

raw, _:= dataChannel.Detach()

OnConnectionStateChange: disconnected ❌ for{ raw.Read()...//blocking }
OnConnectionStateChange: failed ❌ for{ raw.Read()...//blocking }

Active call dataChannel.Close() ❌ for{ raw.Read()...//blocking }
Active call raw.Close() ❌ for{ raw.Read()...//blocking }
Active call peerConnection.Close() ✔ for{ raw.Read()...//Will fail and exit, will not block }

[Sean-Der]

@xdeng The Detached DataChannel API isn't popular with many users like this issue.

The behavior described here is by design. A PeerConnection that has failed can go back to Connecting/Connected! If the user does a ICE Restart.

When the PeerConnection goes to Closed (DTLS Close or PeerConnection.Close() only does that mean that connection is terminally closed.

Sorry about the API frustrations. I am not sure of a better way to do this yet :/

[xdeng]

@Sean-Der Thanks for your answer