On Tue, 2008-07-08 at 15:50 -0500, Duncan McGreggor wrote: > > And while playing around with LDAP/AD, it struck me that Storm actually > > fits quite nicely with a lot of common LDAP uses; AFAIK, you usually > > have a sub-tree for users, another for groups, then computers, DNS, > > etc., and it would be quite nice to package these in Storm classes. Is > > this possible at all, or is Storm tied too closely to SQL? > > > > On a related note: does anybody know of *any* Python ORM for LDAP? > > Remember that the "R" stands for "relational" :-) One could possibly > argue that an LDAP directory is almost an object database. If you > allow for that, then any API for LDAP is kind of like an ORM API for a > relational database...
Granted, LDAP is not relational - but if I asked for a OHM (Object Hierarchical Mapper), nobody would have a clue... Wrapping the Python end in Storm (or similar), would allow for automation of many of the list-packing and unpacking usually going on in LDAP plus the somewhat odd way the API requires updates to be done at times. > The python-ldap lib is the one that I've used most. It has always > suited my needs completely. Have you looked at it at all? > http://python-ldap.sourceforge.net/docs.shtml Per above - a lot of the list-of-lists-folding and unfolding could be simplified greatly and/or hidden completely by the ORM/OHM. (For those lucky souls who have not ventured into the LDAP-world - imagine that every row in a database is in fact an array of values (this allows for multiple e-mail addresses, different ways to spell a name, ...). Very nice when you're the administrator, not so for the programmers.) > That being said, I think your idea is still pretty cool: an LDAP > python API that reflected the storm API... it sure would make LDAP > programming in python more enjoyable :-) My thought exactly! /Siebuhr -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
