> -----Original Message-----
> From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
> Sent: den 2 maj 2000 07:45
> To: Danny Whitesel; [EMAIL PROTECTED]
> Subject: Re: (RADIATOR) Accounting database retry agressiveness...
>
>
<SNIP>
>
>
> Radiator opens a connection to the SQL server and keeps it
> open for as long as
> possible. If the connection goes down, Radiator will reopen
> the connection
> according to the aforementioned timeouts and again keeps the
> connection open for
> as long as possible.
>
> Mike's view tends to be that Radiator should be handling
> radius requests first
> and foremost, rather than wasting time trying to contact SQL hosts.
Probably for some very good reason. However, there are always reasons to trade off in
either direction, so a "nice feature" would be if this was configurable, maybe from
"reconnecct for each request" over some "multidigit seconds value" to "as long as
possible". This would be interesting for load balancing purposes, and for all types of
connections.
IMHO,
Ingvar
>
> hth
>
> Hugh
>
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
