Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "HTTP/1 to HTTP/2 to HTTP/3" video.

  1. Easy enough for browser to expire their connection IDs and negotiate new ones say, every 15 minutes.
    6
  2. 0:17 There was an HTTP/0.9, which left out some of the header structure. I think it was very quickly replaced with HTTP/1.0, which regularized the whole request/response structure.
    3
  3. I wonder why Google didn’t use SCTP for HTTP/3 ... is it because too many existing internet routers only understand TCP and UDP, and nothing else? By the way, no one seems to have mentioned that the original name for HTTP/2 was “SPDY” ... ”SPDY”, then “QUIC” ... geddit?
    1
  4. HTTP is an application (layer-7) protocol, TCP is a transport (layer-4) protocol.
    1
  5. True, but with Open Source, you can just take an existing server or client program (or set of libraries) as the basis for your project, instead of having to reinvent everything from scratch. For example, Python offers loads of toolkits for things like TLS, WebSockets etc that you can reuse. The problem with coming up with your own implementation of some standard protocol is getting it wrong. We saw this a lot with proprietary SMTP, HTTP and DNS products in the 1990s, just for example. Luckily all of them are extinct now.
    1