2009-12-05 18:03:38 PST
As you know, the main problem with torrent trackers is this:
Lets say you are downloading some torrent with 10 files in it and it has no seeder at alll. Your neighbor from the next room seeding exactly the same files but his torrent file from another tracker/made in with with different block size or contain more files than yours (from the same tracker). In this case peers never found each other even if you both using local retracer.
It can be solved if we extend torrent protocol. We need to modify a client, so it will include into torrent file per file hash (TTH for an example, like in Direct Connect) when it creates it (I'm not really sure, is it possible with backwards compability), store on the traker a table [file size-file hash-torrent id in with this file can be found] and add ability to the client to get torrent seeder by file hash (tracker looks in wich torrents a file with needed size/hash present and returns seeder for these torrents).
I think, in the future, it can be improved even more (in case of use DC-like TTH file has): client can implement DC protocol, so torrents can be downloaded from both p2p networks: torrent and DC. Or even DC hub can be integrated into torrent.
What do you think about that?
