[Date Prev][Date Next]
Re: syncrepl and aliases
- To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Subject: Re: syncrepl and aliases
- From: Howard Chu <firstname.lastname@example.org>
- Date: Thu, 04 Nov 2004 01:54:49 -0800
- Cc: openldap-devel@OpenLDAP.org
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com>
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041101
Kurt D. Zeilenga wrote:
At 01:52 AM 10/30/2004, Howard Chu wrote:Thinking about this some more, I see problems with derefFindingBaseObj
as well. Again, if a consumer expects to see entries under a specific
subtree, and the base object is aliased to a different subtree, the DNs
of any returned entries will be "wrong."
I'm still working on rewriting the syncprovider as an overlay. Separating the code out of back-bdb/search.c is proving to be difficult. Just as a matter of principle, should the search scope for a syncrepl search dereference aliases?
This operation does not support alias dereferencing during searching.
The client SHALL specify neverDerefAliases or derefFindingBaseObj for
the SearchRequest derefAliases parameter. The server SHALL treat
other values (e.g., derefInSearching, derefAlways) as protocol errors.
I would guess that a consumer trying to replicate a particular subtree doesn't care about entries outside of that subtree. So entries that only enter the scope by virtue of a deref shouldn't really be considered. If that's the case, evaluating which entries to return can be simplified a fair amount.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support