On Tuesday 02 July 2002 04:04, Oskar wrote:
On Mon, Jul 01, 2002 at 11:26:59PM -0400, Gianni Johansson wrote:
On Monday 01 July 2002 20:21, you wrote:
...
I have read in one post that there is a limit of 60 requests per
minute. It is almost 100 times slower than node could handle
My average bandwidth throttled node settles down to exactly track its
defined long-term weekly traffic limits. Any nodes in contact with it
will be slowed to match it (if they don't lose patience and timeout).
They don't get rejected.
Currently serverSockets get created with a fixed backlog of
On Tue, Jul 02, 2002 at 08:34:53PM +0100, Christopher William Turner wrote:
My average bandwidth throttled node settles down to exactly track its
defined long-term weekly traffic limits. Any nodes in contact with it
will be slowed to match it (if they don't lose patience and timeout).
They
Matthew Toseland wrote:
Very nice. Do our overall per second limits still not work? Last I saw
they set each connection's limit to 10% of the overall limit, but since
we can have many connections, this is unreliable - and also, does
whatever there is now work with your changes?
Yes. The per
On Tue, Jul 02, 2002 at 09:27:03PM +0100, Christopher William Turner wrote:
Matthew Toseland wrote:
Very nice. Do our overall per second limits still not work? Last I saw
they set each connection's limit to 10% of the overall limit, but since
we can have many connections, this is
A new build with non-backwards compatable changes is online as of now,
could everyone please upgrade ASAP.
Thanks,
Ian.
--
Ian Clarke[EMAIL PROTECTED]
Founder Coordinator, The Freenet Projecthttp://freenetproject.org/
Chief Technology Officer,
