What if we tie this into the path shortening code? So if a node is overloaded, instead of dropping queries and connections, it can simply take itself out of the routing path on a couple transfers.
-Pascal Zlatin Balevsky wrote: > This calls for redefinition of an overloaded node. The node should stop > accepting new queries when it runs out of trailing field slots, and > should stop accepting connections when both the RR slots for routing and > the FIFO queues are full. The end result will be that the nodes will be > overloaded much more often, but when they are not they will be serving > trailing fields and sending messages with guaranteed minimum speed of > 1k/sec. So when NGRouting solves the problem with overloaded nodes, we > will be witnessing very low latency on the network and high throughput > speeds. _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
