![]() Moderator ![]()
|
I think it is a problem of lack of specs, if AZ had put out a spec on their DHT implementation, a lot of people would probably have followed that. |
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
No this is not you, Ivan got testing and moddified some checks to see how much it would work. Normally we can only connect to KTorrent 2.0 and up and Mainline 4.1.x and up.
True, but still, they might have had their reasons for not doing that, whatever that might be. uTorrent's kamp probably don't want to get in extra work, plus they have PEX which seems to work pretty well. |
![]() Registered Member ![]()
|
Kick.
utorrent and mainline joined together: http://forum.utorrent.com/viewtopic.php?id=17279 faq Maybe the chance that utorrent will implement the new mainline DHT will rise now that uTorrent and BitTorrent have joined forces. |
![]() Registered Member ![]()
|
The latest SVN should be able to bootstrap from, find, and connect to uTorrent by forcing a DHT ping to all peers it's connecting to regardless of whether or not they've announced that they're DHT-capable.
I've tested it locally on my network with a virgin KTorrent and a swarm of only that ktorrent an a uTorrent LAN machine, and with SVN ktorrent was able to go from 0 to 80 or so DHT nodes in under a minute. |
![]() Registered Member ![]()
|
I know KTorrent now can now more or less get nodes from a utorrent peer, but having utorrent to do native DHT by the BitTorrent spec is what would be even nicer.
![]() Somehow this news got me a feeling utorrent will change it's DHT implementation to the new version. So i thought let's kick the new news in. |
![]() Moderator ![]()
|
Registered users: Bing [Bot], Evergrowing, Google [Bot]