4 ms·
Funny thing, most if not all 'client-side failover' strategies you might find through google or the likes won't work either. This is because the loaded resourc
by 9248 10y ago
Funny thing, most if not all 'client-side failover' strategies you might find through google or the likes won't work either.
This is because the loaded resource will 'fail' anywhere between x seconds up to minutes, or never! In the meantime the user just sees a blank page, or best case, some 80-90% page that keeps trying to load something...
I've experienced this myself a couple times. Most probably my ISP messed up some stuff taking down whole chunks of 'internet' :)
- romaniv 10y agoThe fact that browsers don't have any built-in mechanisms to load-balance resources it disappointing, but not surprising. Think about who are the main drivers of HTML specs. There is probably a way to implement such balancing manually, though. Either through loading parallel documents and exploiting cahcing or through using setTimeout and loading a different set of resources.