Eray Karatay

This branch is using [multiple single-threaded runtimes](https://github.com/programatik29/rewrk/tree/single-thread). Results on my computer: Multiple single threaded runtimes: ``` Beginning round 1... Benchmarking 500 connections @ http://localhost:3000 for 10 second(s) Latencies: Avg Stdev...

Why version 2 when we don't have version 1?

> Should clarify I mean v2 design not version 2 of release Yep. Title is confusing. Do you know any source that I can learn about v2 design?

I think it is out of scope. Keep the issue open for a while in case there is a demand for this.

> When I send http request to my https server, the server just close the connection, reply me nothing, while I expect an error code like 497. You can't use...

I would like to wait until [this issue](https://github.com/hyperium/hyper/issues/2321) is resolved before renaming.

I think `hyperion` would be a good new name for this crate. What do you think?

This library will always be high level server **i**mplementation **on** **hyper** thus **hyperion**. In my opinion it shouldn't be confusing for rust community.

The reason is `hyper`s http future is terminated after upgrade response. Take a look at [`serve_connection`](https://docs.rs/hyper/latest/hyper/server/conn/struct.Http.html#method.serve_connection). This future terminates even if there is an upgraded connection.

I will consider this when or if I plan a new update. This crate might be ported to `hyper-util` in the future. Then I would continue development of this crate...