3 ms·
> For the applications it’s like you can open as many TCP connections as you want without extra overhead from handshakes and rate control start. This sounds a
by breatheoften 8y ago
> For the applications it’s like you can open as many TCP connections as you want without extra overhead from handshakes and rate control start.
This sounds a fascinating claim — is the idea that the programming model when implementing QUIC server applications will allow one to easily aggregate distinct server endpoints which automatically share or amortize the overhead of establishing encryption and congestion detection between all the logical streams used by the application across all the involved nodes?
- tveita 8y agoI mean just between two endpoints, sorry for being imprecise. So instead of opening X TCP connections to a server to run requests in parallel, you'd use one QUIC connection with multiple streams. Much like HTTP 2 does, but using UDP instead of TCP so streams can be ordered and retransmitted separately.