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
Discovery currently works quickly because our current DNS setup works well. But in theory, especially if someone writes a distributed version of discovery, this can be very slow. In the IPFS paradigm, this also often led to confusion—am I not connecting because the address I received from Discovery did not work, OR did Discovery still not respond?
We should ensure we have a reasonable timeout for discovery.
The text was updated successfully, but these errors were encountered:
We have timeouts in our implementation of the discovery trait, but we should include timeouts in our DiscoveryTask (which spawns and runs discovery) so that if other implementations of Discovery don't have timeouts, we have an escape hatch.
Discovery currently works quickly because our current DNS setup works well. But in theory, especially if someone writes a distributed version of discovery, this can be very slow. In the IPFS paradigm, this also often led to confusion—am I not connecting because the address I received from Discovery did not work, OR did Discovery still not respond?
We should ensure we have a reasonable timeout for discovery.
The text was updated successfully, but these errors were encountered: