It is now *six* years ago since I first blogged about how the #QUIC API situation was going to slow down QUIC (and HTTP/3) deployment. Unfortunately I was entirely correct.
daniel.haxx.se/blog/2019/01/21…
The follow-up post a few years later on OpenSSL's decision to be a laggard:
daniel.haxx.se/blog/2021/10/25…
QUIC and missing APIs
I trust you've heard by now that HTTP/3 is coming. It is the next destined HTTP version, targeted to get published as an RFC in July 2019. Not very far off. HTTP/3 will not be done over TCP.daniel.haxx.se
tranzystorekk
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to tranzystorekk • • •kalle
in reply to daniel:// stenberg:// • • •do you have any ballpark numbers? How much slower and resource hungry are we talking about?
+10%? +100%? ×10?
daniel:// stenberg://
in reply to kalle • • •kalle
in reply to daniel:// stenberg:// • • •yooooooo that's impressive. Not sure if ngtcp2 is impressively low or OpenSSL is impressively high, but I guess the latter.
Thanks for elaborating!
Christian Huitema
in reply to daniel:// stenberg:// • • •