Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
UDP tracker
open-in-new
<h2 id="comparison-with-the-http-tracker">Comparison with the HTTP tracker</h2> <p>The UDP tracker is better optimized and puts less strain on the tracking server. Neither tracker has any effect on transfer speeds. </p> <h2 id="clients-implementing-the-protocol">Clients implementing the protocol</h2> <ul><li><a href="/facts/BitComet/UvybCa5U">BitComet</a></li> <li><a href="/facts/BitLord/FcIrxnFt">BitLord</a></li> <li>BitRocket</li> <li>BitSpirit</li> <li><a href="/facts/Deluge_(software)/I7QSU7G9">Deluge</a></li> <li><a href="/facts/FlashGet/6hfsJnPx">FlashGet</a></li> <li><a href="/facts/KTorrent/YKFxT49n">KTorrent</a></li> <li>libbt</li> <li><a href="/facts/Libtorrent_(Rasterbar)/WCjEQTch">Libtorrent (Rasterbar)</a></li> <li><a href="/facts/QBittorrent/0MmRbbsa">qBittorrent</a></li> <li><a href="/facts/Rtorrent/1o0x6HFh">rtorrent</a> (implementing <a href="/facts/LibTorrent_(Rakshasa)/1o0x6HFh">libTorrent (Rakshasa)</a>)</li> <li><a href="/facts/%25CE%259CTorrent/NB05H7Ke">μTorrent</a><a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a></li> <li>Turbo Torrent</li> <li><a href="/facts/Vuze/4ScuT05P">Vuze</a></li> <li>XBT Client</li> <li><a href="/facts/MLDonkey/kEPDhcqQ">MLDonkey</a></li> <li><a href="/facts/Transmission_(BitTorrent_client)/nUHJoYyR">Transmission</a></li> <li><a href="/facts/Tixati/7IxmoLIb">Tixati</a></li></ul> <h2 id="criticisms">Criticisms</h2> <ul><li>Limited <a href="/facts/IPv6/d4dg7kIL">IPv6</a> support (the protocol specifies a 32-bit integer for the IP address and supports <a href="/facts/User_Datagram_Protocol/dxLU0D6q">pseudo-headers</a> for 128-bit IPv6 addresses)</li> <li>No mechanism for <a href="/facts/BitTorrent_index/HP9ChWWW">index</a> sites to scrape an entire tracker <ul><li>This can be supported by traditional TCP scrape mechanisms, as it's not a performance issue.</li></ul></li> <li>No mechanism for trackers to enforce client restrictions</li> <li>The UDP tracker protocol has no field to represent the user agent, as the HTTP protocol has. However, the convention to encode the user agent and version inside the peer_id field still applies.</li> <li>No mechanism for trackers to send warning messages</li> <li>No compression, especially problematic for large announce responses.</li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="http://xbtt.sourceforge.net/udp_tracker_protocol.html">UDP tracker protocol specification</a></li> <li><a href="http://www.dsfc.net/internet/liste-de-trackers-torrent-udp/">an UDP torrent tracker list</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Vilches, Jose (2009-08-12). "First μTorrent 2.0 beta released". TechSpot.com. Retrieved 2009-08-12. <a href="http://www.techspot.com/news/35794-first-%C2%B5torrent-20-beta-released.html" target="_blank">http://www.techspot.com/news/35794-first-%C2%B5torrent-20-beta-released.html</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> </ol>