Currently the situation, even with the recently integrated probabilistic
rejection, is as follows: We start off with no load
We accept some queries
Eventually we use up our outbound bandwidth, and due to either
messageSendTimeRequest or the output bandwidth limit, we reject queries
until our currently transferring requests have been fulfilled.
Your solutions all seem to be addressing the wrong end of this problem by accepting that this situation will happen and trying to make NGR deal with it - but the real question is: Why are nodes getting themselves into a situation where they have to QR solidly for periods of time? The QRing should gradually increase with time such that the situation described above doesn't occur. The probabilistic QRing should be a step in the right direction but if this is still happening even with it then it obviously needs to be tweaked.
Ian.
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
