--- Toad <[EMAIL PROTECTED]> wrote: > > Any other suggestions? Any detail as to why/how a particular option > would work?
Right now when the bandwidth limit is exceeded, all queries are rejected, right? What about if you just stop sending new files. Return a pointer to the node it thinks most likely has the file according to its routing table, or even where it got it from. If the resulting query is successful, the other node should be credited as well (for ngrouting purposes). I guess the idea is that if bandwidth is used up, but cpu isn't, then only bandwidth intensive things should be stopped. On the other hand, if cpu is used up and bandwidth isn't, and we get a request for a key we have, we should still answer it. Checking the local datastore for a key isn't very hard compared to routing, right? 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. > -- > Matthew J Toseland - [EMAIL PROTECTED] > Freenet Project Official Codemonkey - http://freenetproject.org/ > ICTHUS - Nothing is impossible. Our Boss says so. > > ATTACHMENT part 1.2 application/pgp-signature name=signature.asc > _______________________________________________ > Devl mailing list > [EMAIL PROTECTED] > http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
