Closed kitestar closed 8 months ago
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?
This is a duplicate of #279. It's mostly just an oversight when the API was created, and something we'll resolve eventually.
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?