jamesa at daa.com.au
Wed Sep 9 06:35:13 CEST 2009
Michael Ströder wrote:
> Łukasz Mierzwa wrote:
>> I'm writing LDAP library (ORM without R as I call it) for python, it's using
>> python-ldap to do the hard work and let You manage LDAP entries in more ORM
> 1. You're not the first one implementing such a module on top of python-ldap.
> You might want to dig the mailing list's archive to find others.
Yes, I started one, then someone developed it further at
> 2. Most implementations of higher-level APIs fall short with mapping attribute
> type descriptors (OIDs or NAME) to Python class attribute names since they
> ignore the fact that there are sub-types defined in LDAP (;binary and language
> sub-types such as ;de-DE). Also there does not have to be a NAME in an
> attribute type description. So raw OIDs might be returned in a LDAP search result.
> 3. No implementation is dealing correctly with attribute type descriptor
> aliasing with OIDs and several values for NAME. You might want to look at
> ldap.schema.models.Entry to get an idea.
I'm aware of these and chose to ignore them - my library wasn't meant to be
general purpose, it was for scenarios where you have control of the LDAP
server and can make these things can't happen. In fact my ultimate idea was
to upload user-defined model schema to the LDAP server via cn=config.
More information about the python-ldap