Neo26 wrote:I don't use eMule since a lot of time but this feature is from MorphXT right? Anyway let's see what david think about that, this feature rarelly could be useful IMHO... but it could be
Why would you want it?
For torrents created with other torrent maker applications, as soon as the first BitComet peer from a swarm will finish downloading the torrent, it will calculate the eMule hashes for each file of the torrent and make them available to other BitComet peers who may be searching for eDonkey links for that torrent, through the DHT Network. From that point on, every BitComet peer of the swarm should be able to search the DHT Network and retrieve the ED2K links for that task and then search for those files into the eDonkey/Kad Networks, as well.
Good Job, now I know a new feature implemented by NeoKad network.The similar feature of BitComet is closed source and useless to NLthats exactly what NeoLoader does with its own NeoKad network.
Since Bitcoment is closed source, i don't think they will make their DHT extension public such that an other client will be able to querry their hash associations.
For torrents created with BitComet, if at the creation time of the .torrent file the option ”Calculate ED2K link for each file” was enabled (which is its default state) then an “ed2k” key containing an 128 bit eMule hash will be calculated and included into the info dictionary of the .torrent file, for each file of the torrent.
That way, any BitComet peer when decoding the .torrent file will also learn the eMule hashes for each file and thus will be able to search for those files into the eDonkey/Kad Networks.
Users browsing this forum: No registered users and 1 guest