#2059: Deluge not agressive enough during initial (first) tracker update routine
------------------------------------------------------------+---------------
Reporter: AlderaaN | Owner:
Type: feature-request | Status: new
Priority: major | Milestone:
Component: libtorrent | Version:
Keywords: tracker, update, aggressive, timeout, time-out |
------------------------------------------------------------+---------------
Comment(by AlderaaN):
OK,
Following Cas's recommendation to run this by the developer of libtorrent
- I've done so, he has accepted the request and marked it some 30 hours
ago as 'fixed':
http://code.google.com/p/libtorrent/issues/detail?id=301
If you could please coordinate efforts and have it implemented in the next
release - that would be appreciated!
This fix actually negates the need to "babysit" Deluge each time a new
torrent is being passed to it from a Tracker that allows some of its
torrents releases to be listed just before the the main seeder is actually
present in the swarm.
Regards,
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2059#comment:3>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/deluge-dev?hl=en.
