Another idea is to have a queue, and give priority to requests that are closer to one of the node's specialization areas. If all bandwidth is used up, but a new request comes in for a key that we have and is in our specialization, pause the most irrelevant transfer for a while and send that. Wouldn't that also cause ngrouting on the paused node to be less likely to route irrelevant requests later on? Then you would just need code that begins searching for other sources when the transfer drops below an acceptable speed.
This is a fascinating concept worth discussing - but I hate the use of the
word pause. We can have multiple trailers between nodes (hopefully not
too many) and favor one over another in terms of our output rate. Having
our bandwidth "used up" is tantamount to saying there is a lower-limit on
throughput per query/fetch, below which we consider to be unacceptable, or
a DoS. We cannot control the sending rate if we aren't the sender, but we can close connections (=>abort a single fetch) if things are not
productive, and not improving with time. I want to hear more from others.
ken
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
