Better connection reliability
#28 will help with this but other things need to be done as well.
HL is a stateful protocol on either side - this state is stored both server side and client side. We perform L4 load balancing in our deployments in front of HL for protection. Sometimes connections have to reconnect due to a server failure. We should consider a way to resume connection state, potentially on a different server to the one the state was created on. They will have compatible types, but we have to work out how to do this safely (our servers rely on this state for authentication). HL connections should be as reliable as possible, and RPC functions that can't be handled immediately should be queued - the application shouldn't notice reconnects to the server at all.