4 ms·
You are only scratching the surface. The real problem is not for mobile to take over, we can do it, but when to consider wifi down. It is all fun and games if y
by friendzis 10y ago
You are only scratching the surface. The real problem is not for mobile to take over, we can do it, but when to consider wifi down. It is all fun and games if your wireless network is connected to good fiber, but it is not always the case. Internet uplink may be high RTT or flaky itself, it may be low speed and someone started torrent client and video call, it may as well be the very same mobile broadband with "unlimited throttled home" plan, wifi AP can be connected to gateway over multiple wireless hops, etc.. Platform always has to question "is it problem with remote end or uplink? is uplink 2 better than uplink 1?"
Network switch comes with non-zero cost that all connections must be treated reset and have to be reestablished, so even if the platform monitors quality of all uplinks, we still need some uplink stickiness to avoid constant switching between uplinks in places with spotty coverage or flaky uplinks. I'm not saying current status quo is the best, but currently we cannot have it work perfectly.
- Arnt 10y agoTrue, however when you're leaving the building, the most common case ought to be that you stop being able to ping the upstream router. Easy for the phone to find out, since single-hop ICMP doesn't need a long timeout. There are other possible failure modes, of course, but fixing the common case has value.
- andy_ppp 10y agoIt's be good if at the TCP level you could send multiple request packets across different connections on mobile and have whoever got back first was chosen for a while as the default. You have to admit currently this is very clunky. I would also add that specifically for things like Uber it'd be good to set very low network timeouts for Wifi and allow certain apps to suggest to the device they'd like to switch.
- a-priori 10y agohttps://en.wikipedia.org/wiki/Multipath_TCP https://en.wikipedia.org/wiki/Multipath_TCP