new rlm_sql connection pool logic

[Stefan Winter]

Hi,

>
> WARNING: This change breaks compatibility with V2.0 configs, you will
> need an empty pool { } stanza in each instance of rlm_sql
> configuration or the server will fail to load. See
> here https://github.com/alandekok/freeradius-server/blob/master/raddb/modules/sql for
> the full pool configuration sub-section.
>
> The following configuration items no longer have any
> effect: num_sql_socks, connect_failure_retry_delay, lifetime, max_queries.
> Their equivalents are, (start, mix, max, spare), *none* , lifetime, uses.
>
>
> DEVELOPERS NOTE: From this point onwards any new modules which use a
> pool of connections, or would benefit from a pool of connections but
> doesn't use the connection API, will not be accepted.

Sounds nice! Out of curiosity: any plans to make LDAP connections
persistent and pooled as well? one of my customers has very high numbers
of LDAP calls in authorize, and needs to do LDAPS. The TLS session setup
load is very uncomfortable right now.

Greetings,

Stefan Winter

>
> Code for connection pool is here:
> https://github.com/alandekok/freeradius-server/blob/master/src/main/connection.c
>
> #include <freeradius-devel/connection.h>
>
> -Arran
>
> Arran Cudbard-Bell
> a.cudbardb at freeradius.org <mailto:a.cudbardb at freeradius.org>
>
> Betelwiki, Betelwiki, Betelwiki.... http://wiki.freeradius.org/ !
>
>
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20111017/56957e70/attachment.html>