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 (ian, that means you)? Death threats? Note to users: just because maxRoutingSteps=40 and HTL=15, does not mean that it should try to contact 15 nodes. Every time it gets a "cleanly rejected" (QueryRejected), the HTL is reduced by more than a factor of 2.
msg03550/pgp00000.pgp
Description: PGP signature
