We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i see here is no rtt visible in api https://github.com/fluencelabs/fluence/blob/master/connection-pool/src/behaviour.rs . also i see some libp2p setup for ping. what is rule of removing from connected state? like RTT > 30 seconds?
but it could be api feature to allow to decide protocols to route to closes nodes. when connected = false , than RTT = Infinity.
But protocols can cap on 100ms, 1000ms, 10sec 100s sec RTTS to consider on its own what means connected.
The text was updated successfully, but these errors were encountered:
Does Peer.timeout solve this for you?
Peer.timeout
Sorry, something went wrong.
no response
No branches or pull requests
i see here is no rtt visible in api https://github.com/fluencelabs/fluence/blob/master/connection-pool/src/behaviour.rs . also i see some libp2p setup for ping. what is rule of removing from connected state? like RTT > 30 seconds?
but it could be api feature to allow to decide protocols to route to closes nodes. when connected = false , than RTT = Infinity.
But protocols can cap on 100ms, 1000ms, 10sec 100s sec RTTS to consider on its own what means connected.
The text was updated successfully, but these errors were encountered: