On Fri, Nov 07, 2003 at 10:29:45PM -0500, Zlatin Balevsky wrote: > >One radical solution: > >Remove the code to reject queries when the bandwidth limit is exceeded! > > which returns us in the state 5010-5018 where the node has accepted > umpteen transfers, each going at snail speed. Making that prevalent > accross the network will be catastrophic.
Not with NGRouting IMNSHO. > > Another possibility is to go even further back in 5007-5010 where the > node would still accept everything but wouldn't round-robin to the > senders which effectively meant the queries were served in a fifo queue. Heh. > > >NGRouting can figure out when nodes are slow due to long term overload > >a lot more easily and less alchemically than it can deal with query > >rejections. Or so the theory goes. Am I smoking crack here? > > So far NGRouting hasn't demonstrated ability to figure out its head from > its arse (pardon my french). Why not remove all code but NGRouting and > let it figure out everything on its own, including world hunger and > price of fish </sarcasm> Sarcastic remark snipped. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
