QRP question (new Gnutella developer)

"mikeyv_b" <[email protected]>
Newsgroups gmane.network.gnutella.devel
Message-ID <[email protected]>
Hello (again?),

I tried to post the message below as a reply to an old post, but it
seems to have vanished (also a new user to Yahoo Groups, maybe I'm
doing something wrong?). So I'll try reposting it as a completely new
message. Apologies if it appears twice!

***********

Hi all - new Gnutella developer here! Well, an old-new one, I wrote a
Gnutella client back in about 2000, and now we're trying to bring it
back to life by updating it to Gnutella 0.6.

Progress is pretty good, but I have some questions about QRP. The
documentation seems pretty sparse. There is this:

http://www.limewire.org/wiki/index.php?title=QRP

which isn't bad, but it doesn't detail the exact structure of the
messages. There's also this:

http://www.limewire.com/developer/query_routing/keyword%20routing.htm

which seems to detail the message structure, but seems to be horribly
outdated, and I'm not convinced that QRP as implemented closely
matches the method described.

So, here are my questions - I hope someone can help!
1. Do the message structures described in the second document match
the structures used in actual current QRP?
2. I used these structures, and am having a problem. My client is not
reliably receiving searches from Phex, which I'm using as a host to
connect it to for testing. I'm only running in leaf mode at the
moment. Phex is reporting that it's dropping both the reset and patch
messages - on connect, it shows 2 dropped messages, or 0 if I disable
sending of the two QRP messages. Even if I send through a QRP table
that consists of entirely 'allowed' entries, Phex doesn't send queries
through. However, some other clients do - when I connect to wider
Gnutellanet, I receive a flood of queries.

Hoping that someone out there has a suggestion or two - the client is
working fine other than this one remaining problem!

Thanks,

Mike.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.