3 ms·
Slightly off-topic, but I know Google is working on efforts to completely replace TCP with something specifically designed for web applications. Does anyone kno
by meowface 12y ago
Slightly off-topic, but I know Google is working on efforts to completely replace TCP with something specifically designed for web applications. Does anyone know if they also plan on optimizing HTTP 2.0 to fit the new transport protocol they're trying to design, or vice versa?
It's currently implemented as a layer over UDP: http://en.wikipedia.org/wiki/QUIC http://en.wikipedia.org/wiki/QUIC
- pasbesoin 12y agoPerhaps also/more OT, but in the past couple of months I've occasionally observed my Gmail web connection using QUIC instead of TLS. They are already trialing it publicly and in non-beta use (discounting whether Gmail is still "beta") at least in Chrome stable on Linux.
- charleslmunger 12y agoSee this presentation: https://www.youtube.com/watch?v=hQZ-0mXFmk8 https://www.youtube.com/watch?v=hQZ-0mXFmk8 Slides, with quote about why quic is being worked on: https://docs.google.com/presentation/u/0/d/13LSNCCvBijabnn1S4-Bb6wRlm79gN6hnPFHByEXXptk/present?slide=id.g2b4eb9937_815 https://docs.google.com/presentation/u/0/d/13LSNCCvBijabnn1S...
- Lukasa 12y agoWorking well with quic is not a design goal of HTTP/2. However, my understanding is that quic was originally designed to work well with SPDY, and so ought to work well with HTTP/2 as well. There'll definitely be some Googlers paying attention to the WG to ensure that the two protocols play well together.