You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2020. It is now read-only.
An update: at this point, there's no indication that using more than one network connection per client actually improves performance. But client should still re-dial.
How about a different RedialClient that redials if the connection is lost, I could see certain users wanting to know when a connection is lost (the normal Client)?
Actually, now that I'm thinking about it, *ClusterClient with one remote address already does this, albeit with a little more overhead than is strictly necessary.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The client should make a decent effort to re-dial a bad connection.
Perhaps a client should hold more than one connection? (Benchmarking should tell us whether or not that actually improves throughput.)
The text was updated successfully, but these errors were encountered: