hi there,
I've been implementing an extension to RC which may use LDAP (depending on how it was configured). There's already the include/rcube_ldap.php which _seems_ to present itself as a generic interface to LDAP. One problem is that it was implemented with addressbook in mind, so there are lots of fields and behaviors which are useless in other cases when accessing LDAP. The code I'm working on is intended to be integrated into the main tree of RC (so it's not supposed to be just a quick'n'dirty patch). With that in mind, I have two questions: 1. - Is the rcube_ldap class really the standard one for other (non-addressbook) LDAP accesses? 2. - If "yes" to #1, how is the "standard" way to use that to avoid future code breakage? (a code example would be nice) 3. - If "no" to #1, what could be an acceptable solution? A parallel and more generic LDAP class implementation? -- Daniel Mealha Cabrita Divisao de Suporte Tecnico AINFO / Reitoria / UTFPR http://www.utfpr.edu.br _______________________________________________ List info: http://lists.roundcube.net/dev/
