3 ms·
> Latency != bandwidth. yes, and you're conflating the two.
by f2f 12y ago
> Latency != bandwidth.
yes, and you're conflating the two.
- jacquesm 12y agoFrom kjksf's comment above: "That's a lot of http connections which adds up to a lot of bandwidth and time savings." I was only addressing the 'bandwidth' part. The latency bit (which is partially addressed by running multiple concurrent connections via a single socket) is a different issue, for which we also already have multiple solutions (for one, stop making a few hundred requests for a page).
- dcsommer 12y ago> for one, stop making a few hundred requests for a page Telling the world "you're doing it wrong" is not a pragmatic solution. HTTP/2 exists to improve the web as it exists today. In this, it demonstrably succeeds. For the same reason Javascript will remain the assembly language of the web, so too will HTTP/1.1 semantics likely persist forever. It's not because it's what we want but because there is no (yet) known transition away from it. HTTP/2 doesn't replace HTTP/1.1. It just deprecates a horrible wire format and adds some other features.