[µTorrent 1.5 released]

About UDP protocol on tracker:

this in the connection status of the server

pinolallo@xxxxx# netstat -nap tcp | wc -l

10298

pinolallo@xxxxxx# netstat -nap udp | wc -l

7

You will say: but why are asking for udp protol if the connections status for udp has a 1000 times less impact against tcp?

Because effectively the tracker udp traffic is the 33% of the total tracker traffic but has a evident very less impact on the system than tcp/protocol

here the stats of a 6 min of tracker trafic announces monitoring

tcp announces 37588

udp announces 12715

percentile udp/tcp announce ratios ratio 33,8272853

announces/sec 139,73

think about that the tracker respond to a 151 announce+scrape/sec

In my opinion there is a large payoff about udp tracker protocol that should be considered beside the opinion of a "brainDead" protocol spec.

[µTorrent 1.5 released]

dear nTorrent developers, I'm running the largest italian bittorrent community (a village), and we have a problem.

The problem is BitComet. But The solution is not nTorrent because is still missing the udp protocol.

So I'm seriosly thinking about a BitComet tracker wide ban, this because this shity client (also in version 6.3) flood the tracker, distrupt first release superseed launches, announces itself as a new peer entry and many (too many) other nasty things. But for many reasons is an essential need for our community that a client use also udp protocol. nTorrent does not.

I hoped that 1.5 version implemented udp (like azu and BC).

So the question is, UDP protocol will be implemented? There is a beta version where we can help testing the UDP protocol?

Thanks you for writing the definitive BC killer.