And it seems this is the only way.. sigh

However, i thought of a nice route-restore thing in case connections dropped etc.

When you are part of a fork (that is, receive a query twice), you keep the one with the least hops in your route-table. But, you also register the longer route in a backup table.. When the connection with the shortest route drops, you reinstall the longer route to another connection. This would make sure that IF you are able to route it in different ways, you pick the best in all situations. Without this 'fork-awareness' a disconnect of a host would kill lots of routes....

Comments?