I lose ssh and my websockets, but long-polling apps keep working. Kind of ridiculous, but that's the world we live in.
Making your websockets resilient means pinging and aggressive reconnecting.
Or is it just that long polls generally have short timeout compared with what you might implement for a websocket ping?
Setting an alias like "alias sssh='mosh'" greatly helps with muscle memory, too (of course, don't override "ssh", you might still need it).
Funny anecdote: I live in a city called "Moshi"
\sshHere's one hosted Etherpad: https://etherpad.wikimedia.org/
And will be launching a web client in the coming weeks.
So far, so good. We do handle the reconnects ourselves, but otherwise it's been treating us well.
Fortunately wrappers like Socket.io, SockJS, Primus, etc can help with this.
Websockets suck here. BGP routers here flap very often, nuking TCP connections because hey, power cuts. Guess what happens?
Tip: If you're "out to change the world", make sure you can turn your wifi card every 30 seconds and still get a decent-ish experience (yes, long-polling HTTP works, so does good old timer-based polling).