Oskar Sandberg writes:
On Fri, 12 May 2000, Bill Trost wrote:
> As things stand, this RequestFailed has the bizarre property that
> its HopsToLive is *larger* than the RequestFailed that the node
> just received...
This is definitely wrong.
Yup. Never mind, I misunderstood the code. RequestFailed's *do* get
forwarded after all, apparently.
That means that a client inserting a DataRequest with a HopsToLive
of 6 into a test5 network should eventually get a TimedOut
response, not the expected(?) RequestFailed, if I understand the
code correctly *now*. I can't test it against the current node
("RawMessage.java:Error:Stream died while reading message of
type: H??\??1[|5??o??????w????@????eAv????C"), but that is the behavior
I get with the last beta release.
Surprisingly, a HopsToLive of 31 (but not 32) *also* results in a
TimedOut. It looks as though sending a request that results in an
immediate RequestFailed counts as a "hop" for that request.
I don't know if this is "right" or not...
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
