|
|
|
|
|
|
by ezdiy
2986 days ago
|
|
|
HTTP2 is all about "tcp-inside-tcp" states. https://github.com/golang/net/blob/master/http2/http2.go#L81 Wherever possible, they do the sensible thing - just goroutines for each flow, piped into from the muxed frame parser via channels, but the state for each flow must be still tracked as per-flow state in the topmost flow dispatcher - goroutine can't tear itself down on timeouts, inspect OOB signalilng of the topmost stream and such. |
|
|