HTTP/3 is next Generation HTTP. Is it QUIC enough? • Daniel Stenberg • GOTO 2019

This presentation was recorded at GOTO Copenhagen 2019. #GOTOcon #GOTOcph
gotocph.com
Daniel Stenberg - Creator of curl and Receiver of the Polhem Prize
ABSTRACT
HTTP/3 is the designated name for the coming next version of the protocol that is currently under development within the QUIC working group in the IETF.
HTTP/3 is designed to improve in areas where HTTP/2 still has some shortcomings, primarily by changing the transport layer. HTTP/3 is the first major protocol to step away from TCP and instead it uses QUIC.
Daniel Stenberg does a presentation about HTTP/3 and QUIC. Why the new protocols are deemed necessary, how they work, how they change how things are sent over the network and what some of the coming deployment challenges [...]
Download slides and read the full abstract here:
gotocph.com/2019/sessions/953...
/ gotocph
/ goto-
/ gotoconferences
#APIs #HTTP3 #QUIC #IETF #HTTP2 #TCP #Programming
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotocon.com
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
ua-cam.com/users/GotoConf...

[@abhishekjain5354]

I am one minute into the video and already liked it.
He's like, I am the creator of curl, now let's move on to the important topic.
Whaaaaaaaaat!!!!

[@NostraDavid2]

The high CPU usage is *definitely* something that needs fixing. Nobody is waiting for 2-3x CPU usage for a (relatively) small increase in overall performance.

[@autohmae]

You have to remember it only applies for those doing lots of large files like for example UA-cam CDN video files. Everyone else won't really notice.

[@upengan78]

Thank you for sharing this and great presentation too

[@nagyessam1946]

Excellent, very good.

[@idaha9666]

Good presentation

[@phpdude]

Great presentation! Thanks for posting GOTO.. BTW #1 here

[@timrobertson8242]

Daniel, thanks for the clear understanding! I am concerned over the implementation cases. If I have a load balanced website today, the encryption is at the load balancer not the actual website node. Can we run http/2 on that actual web server (unencrypted) and have three load balancer do the repackaging as https/3? Otherwise, I don’t get how this can work.

[@Funnyvideos-fw4uz]

Excellent, very good.

[@zarakhan2066]

Thank you for sharing this and great presentation too