Mike! schrieb:
On Friday 13 June 2008, Christian Lohmaier wrote:
<snip>
Jep, http is blocked intentionally. The torrents we provide for downloaders
have dynamically generated headers, containing the various trackers. That way
the load is balanced across multiple trackers.
I don't understand why you want do make this with dynamically generated
headers. If i look into the documentation of torrent then there is a way
to balance the load to different trackers with only one torrent. I know
some other trackers working with that feature.
A short the a cut of the info of btmakemetafile.py:
announce_list = optional list of redundant/backup tracker URLs, in
the format:
url[,url...][|url[,url...]...]
where URLs separated by commas are all tried first
before the next group of URLs separated by the pipe is
checked.
If none is given, it is assumed you don't want one in
the metafile.
If announce_list is given, clients which support it
will ignore the <announce> value.
Examples:
http://tracker1.com|http://tracker2.com|http://tracker3.com
(tries trackers 1-3 in order)
http://tracker1.com,http://tracker2.com,http://tracker3.com
(tries trackers 1-3 in a randomly selected order)
http://tracker1.com|http://backup1.com,http://backup2.com
(tries tracker 1 first, then tries between the 2
backups randomly)
I would say your looking for the middle example or is there a problem
with this?
My current torrents only have one Tracker inside this means, that only
peers on this tracker will see my seed. And if this tracker is broken,
it would have no more seeds (if every server seed gets this torrent).
<snip>
Mike
Greetings
Bircher Florian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
