2 ms·
In say 5 years, might it be optimal for web browsers to initiate TCP connections to multiple web endpoints, and go with the first to initialise? In fact, brows
by modeless 15y ago
In say 5 years, might it be optimal for web browsers to initiate TCP connections to multiple web endpoints, and go with the first to initialise?
In fact, browsers do something like this today to deal with broken IPv6 implementations, under the name "Happy Eyeballs": http://tools.ietf.org/html/draft-ietf-v6ops-happy-eyeballs-05 http://tools.ietf.org/html/draft-ietf-v6ops-happy-eyeballs-0...
The idea is that if a IPv6 connection isn't established after 300ms then the browser just starts a duplicate connection over IPv4 and uses whichever one comes back sooner.
- colmmacc 15y agoThat's another good example! But 300 ms is nearly four times the limit of human perception. So I do wonder if - as network and service costs diminish - simply using many connections for the same thing won't seem so "wasteful".