(RADIATOR) rate limiting support for Radiator

[Claudio Lapidus]

Hello all,

On Friday, January 14, 2005 8:24 AM, João Pedro Gonçalves wrote:

> Accounting tends to be a lot faster than Authentication, so using
> different instances for Auth and Acct should allow to minimize the
> issues.
>
> The issues we have with bursts and badly configured routers are only
> related to access-requests which take an
> average of 60ms whereas Accounting Requests take an average of 2ms
> (with MySQL sessions enabled) to be processed.

Yes. Even more, authentication and accounting are really different
applications, each with its own needs. For proxy scenarios, we typically set
very aggresive timers for the remote server in the authentication phase,
because we can't afford to wait very much for the response, while in
accounting we can set up many more retransmissions and with longer timeouts,
as we are more concerned with guaranteeing delivery, and it doesn't matter
if the message arrives delayed.

best regards,
cl.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.