5 ms·
The TLS requirement from HTTP2 also hindered http2 origin uptake. The TLS handshake adds latency and is unnecessary on some instances. (This is mentioned in hea
by miyuru 2y ago
The TLS requirement from HTTP2 also hindered http2 origin uptake. The TLS handshake adds latency and is unnecessary on some instances. (This is mentioned in heading "Extra Complexity" in the article)
- tankenmate 2y agoFor HTTP/3 you get 0-RTT however which largely mitigates this.
- stavros 2y ago0-RTT resumption (unless I'm mistaken), which doesn't help with the first connection (but that might be OK).
- rochacon 2y agoCorrect, to achieve 0-RTT the application need to perform the handshake/certificate exchange at least once, otherwise, how would it encrypt the payload? This could be cached preemptively iirc, but it is not worth it. The problem will be that QUIC uses more userland code and UDP is not as optimized as TCP inside kernels. So far, the extra CPU penalty has discouraged me from adopting QUIC everywhere, I've kept it mostly on the edge-out where the network is far less reliable.
- bawolff 2y agoUmm dont you get 0-RTT resumption in all versions of http? Its a TLS feature not an http feature. It does not require QUIC
- deleted 2y ago[deleted]