Re: QRP question (new Gnutella developer)

Quoting Philippe Verdy <[email protected]> from ml.gnutella.dev-forum:
:> De : [email protected] [mailto:[email protected]] De la part
:> de Gregor K.
:> Envoyé : mardi 18 septembre 2007 10:42
:> À : [email protected]
:> Objet : [the_gdf] Re: QRP question (new Gnutella developer)
:> 
:> Hi..
:> 
:> Phex drops QRP messages in case, the host is not reporting to support
:> QRP in the handshake or if the message appears to be invalid e.g. when
:> the messages are not in the right sequence, the patch data failed to
:> inflate correctly or the entry bits value is not 4 or 8.
:
:When the entry bits are not 4 or 8, this should not happen. The recipient
:just need to adjust the entry bits value with a LOWER one.
:
:* If the entry is between 2 and 3, it should then be interpreted as 1
:(meaning that the file will be seeked only on the next connected peer but
:not forwarded to its other peers).
:* If the entry is between 5 and 7, Phex should interpret it as if it was 4.
:* If the entry bits is 9 or higher, it should be interpreted as if it was 8.

I believe you completely misunderstood.

Gregor was not talking about the QRP value, but about the number of bits
that the patch claims to use to encode the QRP values.

Also your reply did not make any sense.  Obviously, anything that is not
infinity in the QRP table means that the query must be forwarded, as TTL is
ignored in the QRP routing (excepted for last-hop QRP routing for Ultrapeers).

Raphael