Which requests should count for load limiting? Load limiting is the process whereby if we get a RejectedOverload or a timeout we reduce the rate at which we send (locally originated) requests, and if we don't, we increase it.
The original intention I think, based loosely on the TCP-over-Ethernet metaphor, was to only count locally originated requests. So if we get a timeout on any other request, this doesn't affect the rate at which we send requests. Is this the best option? It is perhaps closest to "propagate the load back to the originator"? But maybe more information - counting other requests - would be better? -- 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/20060411/580093dd/attachment.pgp>
