No, it isn't. This whole article seems more like a marketing sales pitch than a disclosure.
No, it isn't. This whole article seems more like a marketing sales pitch than a disclosure.
- HTTP/2 as implemented by browsers requires HTTPS, and some people don't like HTTPS.
- HTTP/2 was "designed by a committee" and has: a lot of features and complexity; most of those features were never implemented by most of the servers/clients; most of those advanced features that were implemented were very naive "checkbox implementations" and/or buggy [0]; some were implemented and then turned out to be more harmful than useful, and got dropped (HTTP/2 push in browsers [1]) etc.
[0] https://github.com/andydavies/http2-prioritization-issues
https://en.wikipedia.org/wiki/HTTP_pipelining#Implementation...
But establishing a connection is extremely expensive compared to sending data on an already established channel. With this method they need to open far fewer connections for the same qps.
There's no need to confuse the issue by trying to diagram multiple connections at the same time.