On Thu, Jun 22, 2006 at 07:24:08PM +0100, Michael Rogers wrote: > Matthew Toseland wrote: > >But if the tokens are separate > >from the queue, how is the queue size limited? As far as I can see it is > >necessary that the maximum token bucket size *include* queued/running > >requests as well as possible ones. > > A request is only added to a queue after a token's removed from a > bucket, and a token's only added to a bucket after a request is removed > from a queue, so (total bucket size + total queue size) is constant. Do > we need a further restriction on the number of queue slots each peer can > occupy, given that the number of tokens it receives is already controlled?
Hmmm, okay. Well will it - either the add-to-least-full-bucket or add-to-most-full-non-full-bucket be fair if we only take into account the number of tokens available, and not the queued/running requests? > > 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/20060622/3a74acc2/attachment.pgp>
