Ian and I have agreed to a further change to the HTL mechanism in 0.7, to solve a few problems:
HTL starts off at the maximum value. A request carries the value of the closest location so far seen to the key. When we find a node which is closer than this, we update the location on the request, *and we reset the HTL to the maximum value*. If we go through a node which is not closer than the closest-so-far, we decrement the HTL. If the HTL reaches 0, we send back a DataNotFound. If we cannot find any more nodes, we send back a RouteNotFound. Max HTL can then be as low as 5. There remain probabilistic decrement at maximum and minimum values of HTL. For a subscription request, if we get a DNF and we have reset the closest location, we know we are the closest location to the key, within max HTL hops, therefore we are the root. -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20050923/38b8c2af/attachment.pgp>
