Dnia 2008-07-23, śro o godzinie 16:08 -0700, Mark Doliner pisze:
FYI I just added a stanza rate limit. Instead of limiting based on
the number of bytes it limits based on the combined number of
message, presence and iq requests (regardless of their size).
Cool. I like it very much.
I will
Hmm, two people have told me my last email was empty, so here it is again:
FYI I just added a stanza rate limit. Instead of limiting based on
the number of bytes it limits based on the combined number of message,
presence and iq requests (regardless of their size).
It's configurable in c2s.xml
On Fri, Jul 18, 2008 at 2:23 AM, Tomasz Sterna [EMAIL PROTECTED] wrote:
Dnia 2008-07-11, pią o godzinie 13:48 -0700, Mark Doliner pisze:
1. Don't disconnect people when they hit the rate limit. Instead,
stop reading from their socket until the limit has expired. Do we
have a way to call a
Dnia 2008-07-10, czw o godzinie 17:38 -0700, Mark Doliner pisze:
It
seems weird to me that the router would limit the traffic sent between
the components and the rate at which new components can connect. I'm
in favor of removing this limiting from router for the sake of
simplifying the code
On Sun, Jul 13, 2008 at 1:58 AM, Tomasz Sterna [EMAIL PROTECTED] wrote:
Dnia 2008-07-11, pią o godzinie 13:48 -0700, Mark Doliner pisze:
Do we
have a way to call a function after a certain amount of time has
passed? We would need one for this.
We have time checks in main loop, but this is
On Mon, Jul 7, 2008 at 10:25 AM, Mark Doliner [EMAIL PROTECTED] wrote:
I've been looking at the rate limiting options in c2s.xml, and looking
at the code that intends to enforce those limits. It looks like the
connection rate limit would work (but I haven't tested it), but it
looks like the
