#31 Multitracker handling bug

[Harold Feit]

I noticed two core problems in the multitracker
handling of rufus (possibly carried from g3)

1> Treating the entire announce-list as a single tier.
When announcing, the tiers are separated so as to
identify which trackers share peer data and which ones
don't. Each tier is a group of trackers that share peer
data.

2> Announcing randomly to the announce list instead of
locking on to successful trackers.
Coupled with the above handling of the announce-list,
there is the possibility that you'll end up on all
trackers of an announce-list except 1 when you
disconnect, causing you to continue to recieve incoming
connections for over an hour after you disconnect.

http://bittornado.com/docs/multitracker-spec.txt -
Original Specification
http://wiki.depthstrike.com/index.php/P2P:Protocol:Specifications:Multitracker
- more detailed information.