Announce to multiple trackers at once

[livings124]

uTorrent announces to multiple trackers at the same time.

[charles]

16:22 <@BentMyWookie> alus: ping
16:22 < alus> BentMyWookie: pong
16:23 <@BentMyWookie> i have a question about how utorrent handles multitrackers
16:23 <@BentMyWookie> does it ever connect to multiple trackers at a single time
16:23 < alus> yes
16:23 < alus> well, one tracker a second, but yes
16:23 <@BentMyWookie> i was under the impression the specs say you're not supposed to, and should only connect to one after the previous failed
16:24 < alus> well, uT does not follow the spec there. it's true
16:24 <@BentMyWookie> hmmm
16:24 < wereHamster> alus: are you a uT dev?
16:24 <@BentMyWookie> we've been following the specs to the word after the whole minimum announce fiasco years ago
16:25 <@BentMyWookie> how do you guys not get crap for this?
16:25 < alus> wereHamster: yes
16:25 < alus> BentMyWookie: no single tracker is abused by this behaviour, so no operator has ever complained. we obey the announce interval specification, so a tracker can control load that way
16:26 <@BentMyWookie> is there documentation on what rules utorrent follows for this - does it just announce to all trackers, all in a tier, etc?
16:26 < alus> BentMyWookie: other clients (deluge, in particular) actually "got crap" from users for not behaving like uT does
16:26 < alus> hm. I don't know if there is documentation
16:26 < Gimp_> alus: is there any particular reason you guys chose to go that route? (varying from the spec)
16:26 <@BentMyWookie> we had a couple of users claiming utorrent did this, and i assumed they were wrong
16:26 < alus> Gimp_: it came to us that way, and users seem to like it
16:27 < Gimp_> alus: wouldn't that cause problems with data being transfered though?
16:27 <@BentMyWookie> so does it just announce to all trackers? or do you only announce to those on a tier, or what?
16:27 < Gimp_> alus: I mean reports for transfer amounts. it would announce all data transfered to all trackers
16:27 < Gimp_> alus: but technically a tracker would get transfer numbers that are from peers on a different tracker
16:27 < alus> Gimp_: it's true. we track that per, uh, tracker
16:28 < alus> Gimp_: oh sure. there's no certainty in BT that transfer amounts are related to a particular tracker
16:28 <@BentMyWookie> alus: so does it just announce to all trackers? or do you only announce to those on a tier, or what?
16:29 <@BentMyWookie> and you just announce the same values to all the trackers?
16:29 < alus> BentMyWookie: give me a minute
16:29 <@BentMyWookie> thanks
16:40 < alus> BentMyWookie: sorry, I have to run. I will come back this evening to answer you
16:41 <@BentMyWookie> sure

[charles]

other very useful threads:

​http://forum.bittorrent.org/viewtopic.php?id=17

​http://h33tfr33sp33k.h33t.com/index.php?action=printpage;topic=9210.0

[charles]

An interesting log from the #utorrent channel regarding the multitracker spec

[charles]

updated h33t.com link:

​http://fr33sp33k.h33t.com/index.php?action=printpage;topic=9210.0

[charles]

See also: #2388

[charles]

Added to trunk by r9170 for 1.80

[charles]

09:17 < CIA-22> charles * r9756 libtransmission/ (announcer.c web.c): (trunk libT) #1699 "announce to multiple trackers at once" -- fix minor bug in reporting scrape results when an announce returns enough information that a separate scrape isn't necessary.