Stories
Slash Boxes
Comments

SoylentNews is people

posted by chromas on Tuesday November 27 2018, @09:41PM   Printer-friendly
from the 501-Not-Implemented dept.

curl hacker Daniel Stenberg has announced that his online booklet, HTTP/3 Explained, is available for download from GitHub. The booklet will remain a work in progress as neither the protocol specifications themselves nor any working implmementation are even remotely ready at this moment.

The book describes what HTTP/3 and its underlying transport protocol QUIC are, why they exist, what features they have and how they work. The book is meant to be readable and understandable for most people with a rudimentary level of network knowledge or better.

These protocols are not done yet, there aren't even any implementation of these protocols in the main browsers yet! The book will be updated and extended along the way when things change, implementations mature and the protocols settle.

Earlier on SN:
The Next Version of HTTP Won't be Using TCP (2018)
Google Touts QUIC Protocol (2015)


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Interesting) by driverless on Wednesday November 28 2018, @04:02AM

    by driverless (4770) on Wednesday November 28 2018, @04:02AM (#767192)

    The book describes what HTTP/3 and its underlying transport protocol QUIC are, why they exist

    Oh, that one's easy, to make it easier for large content providers (Google, Facebook, Akamai, Cloudflare) to push content to consumers. Literally. Look at how it's designed and what it does. HTTP/2 was the first step in that direction, HTTP/3 is the final step in the Google-ization of Internet content delivery protocols.

    Which also means that /1.1 will be with us forever, and in fact this was explicitly stated by the /2 WG at the time, "let them eat HTTP/1.1 if they find /2 unnecessarily complex", which was the complaint from pretty much every embedded device and IoT thing developer out there. So now HTTP will be fragmented into three totally incompatible methods, 1.x which will be around forever because anything can do it and it just works, 2 which by the looks of it will be a transient thing while Google forces 3 on us, and then maybe eventually 3.

    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3