Registered Member
|
Here's yet another version of my DHT ping hack, this time I am triggering a portReceived() in socket.cpp on incoming connections, so we can catch a DHT ping for remotely initiated connect, too.
It's a nice feeling connecting to a large torrent and watching those DHT ping messages fly by I also reverted DHT tick marks to their original behavior, and prevented portReceived triggers for port == 0 from peers.cpp (it's already handled correctly in socket.cpp) It's a bit ugly, but it does work.
|
Registered Member
|
|
Moderator
|
Even if peers reply to your ping, that doesn't mean your node count goes up, depending on what bucket the peers ends up it can replace an existing node or none at all if all nodes in that bucket are still active. |
Registered Member
|
|
Moderator
|
|
Registered Member
|
|
Registered Member
|
jdong - great work there, I don't have the coding skill to sit down and hack up additions to kTorrent, but can appreciate what you've done there. Have got the latest SVN compiled and running. Very nice.
Ivan - was that you who contacted the uTorrent devs on their forum? If so, you are a very very patient fellow I really hope that this little DHT issue can be sorted out, the uTorrent group, and especially their users, have a great deal to gain by conforming to the standard as well. Just wanted to let all the dev's know that your time and the work you put into kTorrent is very much appreciated!
"We are the music makers, we are the dreamers of dreams"
|
Registered Member
|
Yeah Well, honestly I was **** having to repeat one damn thing lots of times but in hope everything will work out, I kept my patience somehow... Any volunteers to help with that matter - feel free to jump in discussion |
Registered Member
|
Well, it seems like one of us needs to find this 'ludde' guy that they speak of to advance this discussion any more.... and he's surprisingly missing in action |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar