From @dsmurfin:
To ensure an easy to use and reliable app for the user, it's really important to be able to gracefully recover when a failure occurs. There are several things that could lead to a socket closing you from under us.
TCP server notifies when clients disconnect, but not when the receiving socket itself closes - this can be detected by checking if the notified socket is one of the clients. UDP has no notification functionality at the moment. My proposal here is to extend OSCTCPServer.Notification to add a "closed" case, this would require implementers to support this new case. I'd then look to add this same functionality to OSCUDPServer. We'll also need to deal with safely changing the isListening flag to false.
From @dsmurfin: