Stefan Eissing on Nostr: There is talk about about re-layering the transport parts of HTTP: provide a common ...
There is talk about about re-layering the transport parts of HTTP: provide a common multiplexing, streaming protocol that works over TCP as well as QUIC.
Motivations are twofold:
- extending HTTP now requires double work or breaks at CDNs (they talk QUIC to clients, but not to backends)
- TCP will not go away and HTTP/2 is weak in regard to DoS handling. No one wants to put more effort into extending h2.
So, there might be a HTTP/5 coming on top of a tcp/quic multipleXing thingie (TUIX?).
Motivations are twofold:
- extending HTTP now requires double work or breaks at CDNs (they talk QUIC to clients, but not to backends)
- TCP will not go away and HTTP/2 is weak in regard to DoS handling. No one wants to put more effort into extending h2.
So, there might be a HTTP/5 coming on top of a tcp/quic multipleXing thingie (TUIX?).