Re: (ITS#4115) Connection timeouts in back-ldap and back-meta

[ando@sys-net.it]

On Wed, 2005-12-07 at 14:08 +0000, ando@sys-net.it wrote:

> This is actually a timeout on the select/poll at the ldap_pvt_connect()
> level, so it's not the dual of the idletimeout at the proxy side.  I
> think what you mean could be easily implemented by defining a timeout
> that applies to connection lookup; so, each cached connection could
> carry a timestamp, which is "touched" by setting it to op->o_time any
> time it's being returned by ldap_back_getconn() or meta_back_getconn();
> if the timeout is defined, and op->o_time > lc->lc_time + timeout, the
> connection is dropped and reinitialized.

This is now implemented in HEAD:

	idle-timeout <time>

(hope it is not too similar to the global "idletimeout" directive; in
case, it could be turned into "proxy-idle-timeout"?)

This is a per-database directive for both back-ldap and back-meta; in
back-meta, the per-database directive may be overridden by specific per-
target instances.

p.




Ing. Pierangelo Masarati
Responsabile Open Solution

SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office:   +39.02.23998309          
Mobile:   +39.333.4963172
Email:    pierangelo.masarati@sys-net.it
------------------------------------------