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
client: add connection bookkeeping to Connector for waitAny robustness
Currently, all connection bookkeeping is done opaquely through the network
providers which, in turn, also do this bookkeeping opaquely using system
interfaces (e.g., libev, epoll). Because of this, we cannot handle cases
when waitAny is called and there are no connections (gh-51) or when a
connection has ready responses (gh-132). In order to improve
`waitAny` robustness, we need to add connection bookkeeping to Connector.
We should move the timer start to the beginning of the waiting loop, since
the preceding checking overhead should not be accounted for the waiting
time.
Closes#51
Needed for #132
0 commit comments