From: Michael <mic...@in...> - 2000-02-10 23:59:32
|
Federico Di Gregorio wrote: > > Scavenging the mail folder uncovered Michael Ströder's letter: > > > I'm also planning to write a class library for handling objectClasses, > > attributes and syntaxes. Before I reinvent the wheel it would be nice to > > join a project. > > already done, at least in part. i am planning to write a full validating > system (i.e., you can validate objects *before* trying to write to the > LDAP directory.) I will have a closer look at it as soon as it appears in the CVS. > > I asked about LDAPv3 two days ago. > > i am sorry but i don't know about v3. any urls? RFC2251..2256. (I would not claim having read through all of this.) What IS really of interest that you can retrieve all object classes, attributes and syntaxes with their OIDs existing on a particular LDAP host by reading a schema entry from the root DSE => you don't have to configure the LDAP client to know all the schema definitions. Unfortunately LDAPv3 servers does not provide this functionality to LDAPv2 clients. I don't know how long it takes until the OpenLDAP 2.x series (LDAPv3) gets into a stable state for setting _ldap (ldapmodule.c) on top of this. Can ldapmodule.c can be modified to use Netscape's LDAP SDK instead of the OpenLDAP libs? Actually what I'd like to have is a class library which has base classes for syntaxes, attributes, object classes (inherited object classes in inherited Python classes?) and entries. A LDAP client should be able to handle the schema no matter if it's retrieved via LDAPv3 from the LDAP host or from local configuration (in the case of LDAPv2 access). I plan to rewrite many parts of http://web2ldap.de and that's what I need it for... Ciao, Michael. |