-----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. Cheers, Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFElUE5yua14OQlJ3sRAsWeAJ9CXBuv0J2gNZJ9eh0kQtnUsDk58gCgjr5L H3LwFIQEuuLIKQkib3+J8EA= =Xgx5 -----END PGP SIGNATURE-----
