Re:Can QUIC match TCP’s computational efficiency?
by acdha on Friday May 01, 2020 @03:02PM
(#23045397)
Can you back that up? HTTPS is a requirement for doing anything securely. It seems like a lazy troll to just dismiss it with no explanation. Similarly, even a cursory amount of research into WebSockets or HTTP/2 will turn up real engineering problems which are solved by those protocols. Can you address any of them?
[ Parent
| on HN ]
Re:Can QUIC match TCP’s computational efficiency?
by bullen on Friday May 01, 2020 @06:56PM
(#23047358)
I hash the password with a one-time server salt in the client (instead of HTTPS) and I use simple HTTP comet-stream for real-time data (instead of WebSockets):
HTTP/2 has the TCP head of line problem which makes it completely useless.
HTTP/3 is trying to be more nimble, but it's a protocol! Ossification is a _feature_ of protocols; for TCP it allows the backbone to evolve without everyone re-implementing everything over and over again at the edges!
The solution is to make TCP like UDP instead, by allowing sockets to not resend missed packets.
Another real solution is to remove the network kernel on linux.