We discussed this, but decided that we would rather have a system where you set the htl a little higher and where it contains and absolute control over the number of messages sent because of the request (if the htl is reset on every RequestFailed, then a Request could in theory go on until it has touched the entire network).
On Fri, 12 May 2000, Bill Trost wrote: > The protocol document (section 4.3.2) doth say: > If the pending message store shows that a Request.Data message > with the current UniqeID has already been seen at this node > (indicating a loop in the message's journey), the node must > compose a RequestFailed message in reply inheriting the UniqeID, > HopsToLive, and Depth of the present request. > > Request.java says something similar. > > Aside from the spelling errors, that the RequestFailed should inherit > the HopsToLive makes no sense to me. RequestFailed is a *reply* to the > DataRequest, and should probably get its HopsToLive from the Depth of > the DataRequest; alternatively, since RequestFailed is not technically > "forwarded," it should have a HopsToLive of 1. > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev -- Oskar Sandberg md98-osa at nada.kth.se #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
