News for hackers. Stuff that matters.
Re:Employing QUIC Protocol to Optimize Uber’s App Performance by 7ewis on Monday May 20, 2019 @03:45PM (#19964312)
So is this essentially HTTP/3?
Re:Employing QUIC Protocol to Optimize Uber’s App Performance by wmf on Monday May 20, 2019 @04:07PM (#19964583)
Re:Employing QUIC Protocol to Optimize Uber’s App Performance by tomchristie on Tuesday May 21, 2019 @08:53AM (#19969647)
HTTP/3 is slated as roughly HTTP/2 over QUIC but with some differences as a result. https://tools.ietf.org/html/draft-ietf-quic-http-20#appendix...

I was dissapointed that the article didn't get into any details about the HTTP-level differences, but I think that's basically because they didn't need to know or care about the transport at that level since they were using Google's "cronet" library to dispatch the requests, and Google Cloud Load balancers as the QUIC termination point, so nothing on their ends actually deals with the neccessary differences from HTTP/2.

Re:Employing QUIC Protocol to Optimize Uber’s App Performance by layoutIfNeeded on Monday May 20, 2019 @04:06PM (#19964579)
Why 3? Just call it HTTP-as-defined-by-Google. It worked for HTML!