HTTP/2? about httpbeast HOT 6 CLOSED

It would be nice to start off with http2 in Nim instead of rooting for an upgrade later.

I agree. This is mostly a "for fun" project for me. I have more experience with HTTP/1.1 and want to see how much performance I can wring out of it.

If you want to see HTTP/2 support in Nim then please implement it :)

from httpbeast.

Wouldn't that be realistically faster http by fetching assets in parallel?

Likely, but most of the web is still HTTP/1.1 (and I believe the TechEmpower benchmarks are using HTTP/1.1 as well)

Not aware of any projects that are implementing it.

from httpbeast.

Sure that most of the web is still HTTP/1.1. If you're building this with the intention of scoring higher in a benchmark, that is perfectly valid reason to stick with HTTP/1.1.
However, HTTP/2 is interesting because it is the future, and most of the web servers and browsers already support it for its performance. I run my personal website on nginx with http/2 enabled. and my browser fetches assets in parallel.
It might even help your cause because of header compression. Don't know if there are other hidden costs.
More information: https://http2.akamai.com
https://http2.akamai.com/demo

Http/2 support matrix: https://github.com/http2/http2-spec/wiki/Implementations

"Starting with Go 1.6, the http package has transparent support for the HTTP/2 protocol when using HTTPS. " - Not that everything Golang does is for the best.
It would be nice to start off with http2 in Nim instead of rooting for an upgrade later.

from httpbeast.

It's 2022, any changes?

from httpbeast.

Nope. No plans for HTTP/2 from me at least.

from httpbeast.

@dom96 I'm more interested in development a new http server (I would be a good task to understand protocol better) with http2 support. Do you see any significant design flaws in current httpbeast design? What would you do different if you would start working oh http server from the scratch?

from httpbeast.