QUIC is HTTP 2 over UDP
daniel.haxx.se
daniel.haxx.se
My current estimation is that webservers would need to have 3 completely different implementations of the HTTP stack (for HTTP/1.1, HTTP/2 and HTTP/QUIC), where only the most upper layer (interfaces for sending requests and respones) can be shared, the remaining stuff will be very different.
Because it's made for speed issues right?
> QUIC has implemented its own identifier for unique connections called the Connection UUID. It's possible to go from WiFi to LTE and still keep your Connection UUID, so no need to renegotiate the connection or TLS. Your previous connection is still valid.
This sounds more viable than Multipath TCP.
Also not relying on the rightfully conservative TCP standard, they can iterate over new ideas. I thought the area should be thoroughly examined by now. But they have another good idea:
Forward error correction. This is essentially RAID 5 on the network level. This introduces an overhead of 10 % so one in tenth packages might be lost. However this saves us from a costly roundtrip. My knowledge of networking is a bit rusty but this is not implemented in TCP I suppose.
Anybody got any idea of when support for this will arrive to more mainstream servers. Such as apache?