We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
func (l *listener) Accept() (net.Conn, error) { c, raddr, err := l.parent.Accept() if err != nil { return nil, err } return Server(c, raddr, l.config) }
Server() ---> createConn ---> handshake use synchronous handshaking
Server() ---> createConn ---> handshake
If one connection's handshake times out, it directly affects the next connection's accept.
Why not use an asynchronous handshake when accepting a connection?
The text was updated successfully, but these errors were encountered:
This is a duplicate of #279. It's mostly just an oversight when the API was created, and something we'll resolve eventually.
Sorry, something went wrong.
No branches or pull requests
Server() ---> createConn ---> handshake
use synchronous handshakingIf one connection's handshake times out, it directly affects the next connection's accept.
Why not use an asynchronous handshake when accepting a connection?
The text was updated successfully, but these errors were encountered: