As a bit of a historical note, we always intended Zend_Ldap to be a placeholder for a full LDAP client implementation. What was contributed for 1.5 was only the functionality needed to bind, thereby authenticating a user, to an LDAP server. We felt it would be awkward to have all of this code in the LDAP Zend_Auth_Adapter folder, since we fully expected someone like Stephan to come by and fill out our LDAP support.. Please, Stephan, feel free to add whatever functionality you need to either existing classes or folders where it makes sense. As long as it’s all BC in the end. J
,Wil From: Stefan Gehrig [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 12:59 PM To: 'Matthew Ratzloff' Cc: 'Zend Framework' Subject: AW: [fw-general] Extended Zend_Ldap component in Standard Incubator Hi Matt, the component will be called ‘Zend_Ldap’ as it currently is a merge of first proposed Zend_Ldap_Ext and the current Zend_Ldap. It’s a replacement, 100% backwards-compatible, for the current Zend_Ldap – as proposed by Ralph Schindler in his comment announcing the approval of the component into the Standard Incubator. Best regards Stefan Von: Matthew Ratzloff [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 7. Dezember 2008 21:51 An: Stefan Gehrig Cc: Zend Framework Betreff: Re: [fw-general] Extended Zend_Ldap component in Standard Incubator Can I suggest calling it Zend_Ldap_Extended instead? In the PHP world "ext" implies "PHP extension", e.g., ext/ldap. "Extended" would remove any possible confusion about its purpose. -Matt On Sun, Dec 7, 2008 at 6:33 AM, Stefan Gehrig <[EMAIL PROTECTED]> wrote: Hello everybody, after having been accepted for Zend Standard Incubator development the proposed extended Zend_Ldap component (formerly known as Zend_Ldap_Ext) has been moved to the Standard Incubator for further development. Overview: The existing Zend_Ldap component currently just responds to authentication use cases in all their varieties. There is no posibility to query a LDAP directory service in a unified and consistent way. The current component also lacks core CRUD (Create, Retrieve, Update and Delete) functionality - operations that are crucial to for example database abstraction layers. This proposals tries to resolve these deficiencies in that it provides a simple two-ply object oriented model to connect to, query and perfom CRUD operations on an LDAP server. The first layer is a wrapper around the ext/ldap functions, spiced up with extended functionality such as copying and moving (renaming in a LDAP context) nodes and subtrees. The second layer (Zend_Ldap_Node) provides an active-record-like interface to LDAP entries and stresses the tree-structure of LDAP data in providing (recursive) tree traversal methods. To simplify the usage of the unfamiliar LDAP filter syntax this components proposes an object oriented approach to LDAP filter string generation, which can loosely be compared to Zend_Db_Select. Usefull helper classes for creating and modifying LDAP DNs and converting attribute values complete this component. Furthermore it is possible to do some LDAP schema browsing and to read and write LDIF files. It is important to note, that this proposal is a complete replacement for the current Zend_Ldap component and does not break backwards-compatibility. For further information please take a look at the proposal page: http://framework.zend.com/wiki/display/ZFPROP/Extended+Zend_Ldap+Proposal+-+ Stefan+Gehrig The next development step will be to separate the ext/ldap function calls from the core component and move them into an own adapter class to allow for other adapters (e.g. testing adapter with no real LDAP connection) to be attached to a Zend_Ldap object. Feel free to try and test the component - feedback is always appreciated! I'm especially interested in tests against other LDAP servers than OpenLDAP, which is the only one currently available to me for development. Best regards Stefan -- Stefan Gehrig [EMAIL PROTECTED]
