On Sun, Jun 18, 2006 at 01:04:09PM +0100, Michael Rogers wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Matthew Toseland wrote: > > It also has a small > > token bucket, simply to smooth things out a bit; every time we would > > have an opportunity to send a request, we add a token. > > This isn't something we've discussed... > > > INCOMING REQUESTS: (load limiting) > > For each node (and also for the local node), we keep another token > > bucket. If this node sends us a request, we remove a token from its > > bucket; if there are no tokens left, we reject the request with > > RejectedOverload. > > Every time the number of tokens in the bucket changes, we inform the > peer. Normally it shouldn't send us requests when its bucket is empty, > but it's possible if packets cross on the wire. The number of tokens in > the bucket at the far end of the link is analogous to the receiver > window in TCP: you only send a request if it's allowed by the AIMD *and* > there's a token available at the other end of the link.
That may be a useful mechanism, but it's not essential, and we need to decide how to deal with misrouting first. > > Cheers, > Michael -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20060620/9373fcd5/attachment.pgp>
