Lee writes: > Here's a possible way to make "Depth" useful: have the originator of > a Request set it to a small random value (say 1-10). On each forward > hop of the request, Depth is incremented as HopsToLive is decremented-- > but unlike HopsToLive, it is not further incremented on subsequent message > forwards in response to RequestFailed's, so it really does represent the > current distance from origin of the request (+ the random starting > value). Replies, then, can use it to set HopsToLive to an efficient value > (and replies themselves will not have a Depth). Will this work the way I > think it does, or am I missing something?
I think it does work this way, at least approxmimately. It looks like the depth is not incremented upon getting RequestFailed, it is copied from KeyedMM.depth which was set when the Request message came in. One problem: we want to set the original depth to a small random value, in the range 1-10. This is so the 2nd node can't tell that the message came from the first node, maybe it was being forwarded from someone else. But we better not set depth to 1 in that case! If depth happens to be 1 then that will prove the request came from that first node. So we should set depth to a small random value, in the range 2-10. But now we better not set it to 2! Since that is now the lowest value it will only happen if the message originated in the source node and was not being forwarded. So we should set depth to a small random value, in the range 3-10... Hal _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
