dswij

> @seanmonstar If hyper can't be used without the code, then maybe it shouldn't live in a separate `hyper_util` ? The whole idea is to allow users to easily choose...

@seanmonstar or perhaps we can point users directly to `hyper-util` crate for examples? with a note saying hyper itself is for a lower-level usecase

We provided a simple Tokio runtime implementations in [hyper-util](https://docs.rs/hyper-util/latest/hyper_util/rt/index.html). This is not a third-party library, it's maintained by hyper's maintainers.

It is safe to use with hyper 1.0.

The example Timer implementation for `Tokio` is a working example. The module is private, but we're exposing `hyper::rt::{Sleep, Timer}` [here](https://github.com/hyperium/hyper/blob/7206fe30302937075c51c16a69d1eb3bbce6a671/src/rt/mod.rs#L15), which is what you'd need to implement this.

That's fair. The doc for `rt::{Timer,Sleep}` is also asked in #3411.

The docs for hyper::rt will be added in https://github.com/hyperium/hyperium.github.io/pull/121. Will close this issue since we're also tracking it in #3411, and `header_read_timeout` docs were updated. Thanks for the report @jorendorff...

The server itself does not hang when a client close the connection abruptly, but there isn't a good way to see the error in hyper 0.14. In hyper v1.0.1, it...

@silence-coding are you still getting this flow control problem recently? If so, can you help to test out with the current version of h2? I tried reproducing locally and can't...

Yes. Setting a low `concurrency_limit` together with a high `maximum_concurrent_streams` in `tonic` will result in a deadlock. Here, it's because the concurrency limit is lower than the default HTTP/2 max...