[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4070) back-ldap should resolve referrals itself

On Sat, 2005-10-08 at 16:10 +0000, hyc@OpenLDAP.org wrote:

> Watching test039 run, and with some of the discussion about detecting chaining
> loops, it's clear that back-ldap should not be relying on libldap to chase
> referrals. Instead back-ldap should manage them along with the rest of its pool
> of connections.

This should now be fixed in HEAD: use slapo-chain also with back-ldap.
Slapo-chain now recursively chains referrals, and provides a simple
means to limit too long chains.

Note that now back-ldap & back-meta don't chase referrals by default.

> Also the connection record should contain some kind of "last
> contacted" timestamp along with server status, so we can reduce the number of
> attempts to connect to unavailable servers. (E.g., if server_status == DOWN &&
> now - last_contacted < 30, ignore...)


> There's still a separate question of how to deal with chaining loops, e.g.
> pointing two back-ldap installations at each other. No referrals are involved
> there, so the only solution requires adding state to the requests (e.g.
> chainingArguments).


Ing. Pierangelo Masarati
Responsabile Open Solution
OpenLDAP Core Team

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