5 ms·
In my head the main benefit of QUIC was always multipath, aka the ability to switch interfaces on demand without losing the connection. There's MPTCP but who kn
by infogulch 2y ago
In my head the main benefit of QUIC was always multipath, aka the ability to switch interfaces on demand without losing the connection. There's MPTCP but who knows how viable it is.
- rocqua 2y agoMptcp sees use in the Telco space, so they probably know.
- modeless 2y agoIs that actually implemented and working in practice? My connection still hangs whenever my wifi goes out of range...
- Sesse__ 2y agoApple's Siri is using MPTCP, so it is presumably viable.
- jshier 2y agoIt requires explicit backend support, and Apple supports it for many of their services, but I've never seen another public API that does. Anyone have any examples?
- mh- 2y agoLast I looked into this (many years), ELB/GLBs didn't support it on AWS/GCP respectively. That prevented us from further considering implementing it at the time (mobile app -> AWS-hosted EC2 instances behind an ELB). Not sure if that's changed, but at the time it wasn't worth having to consider rolling our own LBs. To answer your original question, no, I haven't (knowingly) seen it on any public APIs.
- suprjami 2y agoI always thought the main benefit of QUIC was to encrypt the important part of the transport header, so endpoints control their own destiny, not some middle device. If I had a dollar for every firewall vendor who thought dropping TCP retransmissions or TCP Reset was a good idea...