[Date Prev][Date Next]
- To: openldap-technical <email@example.com>
- Subject: MDB distribution
- From: "Brett @Google" <firstname.lastname@example.org>
- Date: Mon, 14 Nov 2011 16:32:20 +0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=2ObiibqxN47+9BuXKpN6jbqg40sBehpiHSZ3B14AgMI=; b=U26+zlLh21jMRlxvLCYCXmiuOEQ9R9o9qBi8aW21iXwc3IGH2lqIVQxsfWS8v/kqTU Uj2iRGL/6p1PR4BjoYi2oSJHKlS2HpeSSAnQrGgKsHYqQar1Mz86h+0Y/HvsZsWxnXrV X0o4RzX5PlrhBhtjAl4lnRh2FE6B8fBGcFE8k=
On Mon, Nov 14, 2011 at 3:20 PM, Howard Chu <email@example.com>
Brett @Google wrote:
This point is false; libmdb builds on its own and is intended for use in more than just OpenLDAP. (I already spelled this out in my LDAPCon presentation...) I've ported SQLite to use it, for example, and I will be porting it to Cyrus SASL (sasldb), Heimdal, and various other miscellaneous stuff that comes along. The API is fully documented in Doxygen, and part of the reason I went to that trouble was to ensure that other programmers could use it easily.
Sorry for the "fuzzy" logic :P, but :
My thoughts for no:
1. The name will affect only the name of the backend module, which is
logically a unit under the scope of openldap (and all backends share a
prefix), it can't exist by itself.
Mmm. That sounds interesting. I have only just read your LDAPCon presentation, i have been away. Will the source for mmdb library itself eventually live separately somewhere, or just bundled with ldap ?
The only thing that interferes with my learning is my education.