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

back-ldap and rewrite/remap in 2.3

[reposting with subject; sorry]

Regarding ITS#3350 (and partially my previous posting), I'd like, for 2.3,
to remove DN rewrite and attribute mapping code from back-ldap, since it's
now handled by the rwm overlay, with equivalent (and improved)
functionality.  The same stuff cannot yet be removed from back-meta
without changing the configuration and the functionality because in
back-meta it occurs at and after target resolution, with separate rewrite
configuration for each target, so inside the backend functonality. 
However, my long term plans for back-meta are to replace it with multiple
instances of back-ldap glued together by the backglue framework.

I already have a version of back-ldap with the rwm functionality backed
out; I wonder what's the best way to proceed: should I just replace the
current back-ldap code, or have it in parallel with the original one until
the overall setup (slim back-ldap + rwm) proves to have the same
functionality and reliability?  I'd avoid having all the rewrite stuff
conditionally compiled in, because it's going to be very messy, since
removing the rwm functionality really makes back-ldap very very clean: a
straight use of the Operation members into the client API.



Pierangelo Masarati

Pierangelo Masarati

    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497