4 ms·
Most interactive webapps such as gmail send many HTTP requests. And those requests do not have to be over the same TCP connection. So the webapp could continue
by Buge 10y ago
Most interactive webapps such as gmail send many HTTP requests. And those requests do not have to be over the same TCP connection. So the webapp could continue to work even if you change IPs. Any requests going at the time of the change would fail, but ideally the javascript of the app would retry them.
- JdeBP 10y agoYou've glossed over the part about TCP connections. Try roaming whilst one of those HTTP transactions is in progress.
- Shish2k 10y ago> Try roaming whilst one of those HTTP transactions is in progress That specific connection silently fails, then the app silently retries, and succeeds - from the end user's perspective, they've switched IP addresses and the webapp still works fine.
- JdeBP 10y agoIncorrect. TCP does not work that way and the failure mode is nowhere near that smooth. I suggest actually trying it. No cheating and watching Keith Winstein's video on the mosh WWW site, which shows what actually happened in the case of one fairly well-known WWW app, now! (-:
- moosingin3space 10y agoOn my Android phone, the user experience is significantly degraded when that happens -- the app has to wait to re-establish a TCP and TLS connection, which is relatively slow.