What the OP was talking about, which I totally agree with, is protocols that can't tolerate interruptions to their connection. This can be done with TCP. When

What the OP was talking about, which I totally agree with, is protocols that can't tolerate interruptions to their connection. This can be done with TCP. When I worked in an office, I had the same issue as the OP - docking/undocking my laptop resulted in switching from wired to wireless, and connections (eg: SSH, RDP) would often drop. I ended up unplugging the ethernet at my desk and using wireless most of the time because it was just easier. What would help is protocols actually support the concept of a "reconnection" -- ie: a TCP session that has the same identifier or token as a previous one that lets it it silently resume instead of starting fresh with new authentication. This isn't even that hard to implement if designed in from the start.