On Mon, Jul 29, 2002 at 05:13:59PM +0100, Matthew Toseland wrote:
> maxRoutingSteps should not include steps rejected because they point
> back to the requestor.
> Pro:
> Should prevent RouteNotFound, attempts were made to contact 0 nodes
> Con:
> Requests may get routed too far away from the idea
maxRoutingSteps should not include steps rejected because they point
back to the requestor.
Pro:
Should prevent RouteNotFound, attempts were made to contact 0 nodes
Con:
Requests may get routed too far away from the ideal route.
This is in the new build 490.
Comments? Revocation notices? Flames
