[Date Prev][Date Next]
Re: release 2.2.1 and roadmap
thanx a lot for replying.
re: LDAP Sync, content synchronization - see the new Admin Guide for
This feature supports a pull-based replication model built in to slapd.
(Apopposed to push using slurpd.)
Is that what mutimaster replication ment to be? And where can I find new
Admin Guide? Sorry, I checked again documentation part of the
www.openldap.org and could not find it there, must be hidden somewhere I
Best regards, vadim tarassov.
Howard Chu wrote:
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of
In the roadmap you write
OpenLDAP 2.2 (~2Q2003)
Functional enhancements and improved scalability:
* "LDAP Sync"-based Lightweight Replication
* NS-SLAPI Support
* Proxy Cache Support
* Hierarchical Backend
* Backend Layering
* LDAPv3 extensions:
* ACID extensions
* Cancel Operation
* Content Synchronization Operation
* DIT Content Rules
* Duplicate Entry Extension
* Simple Paged Results Extension
* Proxy Authorization Extension
Does anyone know what is "LDAP Sync"-based Lightwight
Replication? And what is Hierarchical backend? What is
backend layering? What is NS-SLAPI support? What is content
synchronization operation? Is all of this available in 2.2.1?
re: LDAP Sync, content synchronization - see the new Admin Guide for details.
This feature supports a pull-based replication model built in to slapd. (As
opposed to push using slurpd.)
re: Hierarchical backend (aka back-hdb: "h" stands for "hierarchical" or
"Howard's" depending on who you ask...) - this is a new evolution of back-bdb
that uses a hierarchical database layout instead of the flat layout that
back-bdb and back-ldbm use. The new design speeds up add/delete/modrdn
operations, and also supports (for the first time in OpenLDAP) subtree
rename. Another side effect of this development is that both back-bdb and
back-hdb fully support Aliases. (Aliases were not yet implemented in 2.1
back-bdb, and the implementation in back-ldbm is flawed.)
re: backend layering - this is a feature of the new slapd internal API which
allows modules to be stacked on top of each other to provide new
functionality. One example of its use is included in the code - it stacks
back-ldap on top of any other backend to perform very simple Chaining: if you
configure "overlay chain" on another backend, then whenever that backend
returns an LDAP_REFERRAL return code back-ldap will intercept the result,
parse the referral, chase it, and return that result instead. This new API
mechanism allows very complex behaviors to be built up using any existing
backends plus a small amount of glue code. Other features will be developed
using this mechanism down the road.
re: NS-SLAPI - this is a port of the Netscape plugin API to allow using
Netscape/iPlanet slapd plugins in OpenLDAP.
Some other folks can give you more information on LDAP-Sync and NS-SLAPI...
I should note that back-hdb and the NS-SLAPI support in 2.2.1 have a couple
memory /resource leaks that are fixed in CVS. If you really want to use this
stuff you may want to get the newest code from there instead.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support