I truly enjoyed reading this article, it is very detailed yet easy to read, thanks you for this.
I had no idea which is which, and thanks to you I remember it like this-
HTTP- old, terrible at long distances, loads one at a time
HTTP/2- noice, okayish at long distances, loads multiple at a time, though might resend packets since there’s no packet verification when multiplexing (hidden below TCP). Also, heavy server usage due to parallelism.
HTTP/3- the future, blazingly fast anywhere, loads multiple at a time, uses the QUIC protocol which is based on UDP.
I truly enjoyed reading this article, it is very detailed yet easy to read, thanks you for this.
I had no idea which is which, and thanks to you I remember it like this-
HTTP- old, terrible at long distances, loads one at a time
HTTP/2- noice, okayish at long distances, loads multiple at a time, though might resend packets since there’s no packet verification when multiplexing (hidden below TCP). Also, heavy server usage due to parallelism.
HTTP/3- the future, blazingly fast anywhere, loads multiple at a time, uses the QUIC protocol which is based on UDP.
See that? ☝🏻You did that, thank you!
Brilliant!