Two ideas: 1) Reuse NGR code to let the node keep statistics on itself like it's neighbors do. The quality of this estimate would be far better than that a neighbor can make, because it knows about all the queries it handles, and it has a long time to same data, since it can't disconnect from itself :-).
Reject queries for things outside your specialization first. This should teach other nodes quickly what your specialization is. This should also hurt less than rejecting randomly, since things outside your specialization can obviously be routed else where anyway. Is this a lot of work? Does the idea seem sound? 2) On every rejection message send some feedback giving a quota for how many queries max should be sent. Then the other node could just "prereject" queries for you. This number could be in queries per second or perhaps better queries outstanding QS. For example: if QS=10, I can send you 10 queries, but after that I have to wait until you reject, accept, say something about them. __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingelt�ne f�rs Handy bei http://sms.yahoo.de _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
