[BitTorrent] Tracker-hub implementation?

Harold Feit - Depthstrike.com Administrator dwknight at depthstrike.com
Tue Nov 30 18:32:22 EST 2004

Hash: SHA1

Multiple trackers acting as one already has current, real-world
deployed tested and functioning, implementations.
The multitracker specification that John Hoffman (TheShad0w) has
written is used for one method of enabling this "tracker farm"
deployment. (read: http://bittornado.com/docs/multitracker-spec.txt )
Another option that can be used if all the trackers in the farm have
static IP addresses is round-robin DNS. This enables multiple
trackers to act as one seamlessly with all clients.

The BitTornado source package ( http://bittornado.com ) includes one
method of linking trackers, but is extremely inefficient and very
abusive to each tracker in the network, gathering peer data by
appearing to be a client to get batches of peers and adding to its
internal database. This method is VERY abusive to trackers.

Some versions BNBT (specifically 7.3, 7.7, and 8.0;
http://bnbt.go-dedicated.com ) and trackers based on those versions
have much more efficient ways to link trackers available, relaying
peer data between each other. All communication between trackers
happens over a persistent link in a similar fashion to IRC, although
using a propietary protocol to do so. Currently it does not support
linking multiple tracker hubs to each other, it only supports 1 hub
with 64 leaves (as far as I have checked).

* moves this suggestion from "would be nice to implement" to "is
implemented, but is uncommon"

- -----Original Message-----
From: Adam Lyttle [mailto:adam at lyttlesoft.com] 
Sent: Tuesday, November 30, 2004 5:28 PM
To: BitTorrent at yahoogroups.com
Subject: [BitTorrent] Tracker-hub implementation?

This is basically a theory that came to me while I was looking over
the Bittorrent protocol. The idea is to be able to specify a
'tracker-hub' or 'tracker-hubs' for BitTorrent clients. These hubs
would be like the general trackers that we see now, however they
be configured to handle and categorize any info_hash. Their function
would be to serve as a backup or mirror to the tracker(s) specified
the torrent file.

The tracker-hubs would be used as an additional source of peer ip's
and as a backup source if the main tracker goes down or offline. This
would effectively bring the BitTorrent protocol one step closer to a
truely decentralised peer-to-peer network.

Implementing a feature like this would be relatively easy, but to
truely get the most out of it some of the more popular BitTorrent
clients would have to support it.

What do you think?

- -- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.289 / Virus Database: 265.4.3 - Release Date: 11/26/2004

Version: PGP 8.0.3


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!

Yahoo! Groups Links

<*> To visit your group on the web, go to:

<*> To unsubscribe from this group, send an email to:
    BitTorrent-unsubscribe at yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:

More information about the BitTorrent mailing list