Skip to content

HTTP 1, 2, and 3 #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
philsturgeon opened this issue Feb 6, 2025 · 0 comments
Open

HTTP 1, 2, and 3 #91

philsturgeon opened this issue Feb 6, 2025 · 0 comments
Assignees

Comments

@philsturgeon
Copy link
Contributor

philsturgeon commented Feb 6, 2025

Braindump found in some notes somewhere, not entirely sure I know wtf I'm getting at here but here it is until I have something better. Chip in folks.


Http 0.9 pretty much just static docs
Http 1.0 what did it improve I guess Ajax now
Http 1.1 keep alive 10% improvement, lots of clients don’t use it, Wework graph, the gold standard until spa meant lots of connections, browser limitations
Lack of knowledge about keep alive has lead to folks batching requests to avoid “handshakes” which is often actually slower

Let’s stop building to take into to http2, leave model design until later

H2 allows multiplexing so lots of requests made over same connection and responses are mixed together, browser solves max connections from hard set 6- to confugurable 100

H2 hpack means headers are squashed (handy if you have big JWT and other session data, but try to avoid that anyway), and server push is awesome. Please push mention.

Http 0.9 going away

curl/curl#4191

@philsturgeon philsturgeon self-assigned this Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant