Skip to content
New issue

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

[CLOSED] start *before* dht is ready #131

Closed
feross opened this issue Sep 21, 2014 · 1 comment
Closed

[CLOSED] start *before* dht is ready #131

feross opened this issue Sep 21, 2014 · 1 comment
Labels

Comments

@feross
Copy link
Member

@feross feross commented Sep 21, 2014

Issue by feross
Friday Jul 25, 2014 at 12:33 GMT
Originally opened as https://github.com/feross/bittorrent-client/issues/35


Right now, 'ready' is not emitted until the dht emits 'ready' (which happens when the routing table is sufficiently populated).

We're delaying client.add() calls until 'ready' fires, which slows down download start for torrents/magnet uris that have tracker urls. These should start using the tracker urls ASAP and use the DHT once it's initialized in 3-10 seconds.

@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Sep 21, 2014

Comment by feross
Sunday Aug 17, 2014 at 08:26 GMT


Done! Download starts way faster now because trackers can be used immediately instead of after the initial DHT crawl.

@feross feross added the enhancement label Sep 21, 2014
@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.