Le 27/06/16 à 12:15, Howard Chu a écrit :
> Emmanuel Lécharny wrote:
>> Le 27/06/16 à 08:07, Zheng, Kai a écrit :
>>> Thanks for the update.
>>>
>>> It looks like to me there is much work to do. Is there any
>>> alternative option? I'm still thinking that if we could leverage any
>>> existing back end implementation, so we could focus on the LDAP
>>> specific logic for the master server component...this is worth being
>>> considered because in today's industry there are so many B-TREE's
>>> implementations already.
>> I think we already discussed that matter months ago. I also think that
>> many don't understand why we *need* somthing like Mavibot. But let me
>> try to explain again...
>
> As an aside, there are two things going on here - you need both an
> underlying DB engine, and you need an LDAP-centric "backend" on top of
> it. Even if you tried to plug in an off-the-shelf DB engine, you still
> need to implement the backend that uses it.
We have the abstracted layer for a decade now. That allowed us to use a
LDIF based backend, a JDBM backend, a BerkeleyDB backend, An Oracle
RDBMS backend and a Mavibot backend, beside a in-memory backend. And,
yes, this is a mandatory piece of the puzzle.
