Daniel Mealha Cabrita wrote: > Thomas, > > I've sent an email on this very subject to the devel mailing list, > unfortunately I've got no response.
I'm sorry for that but I cannot answer every post there. Don't expect your mails being answered within a couple of days. > > Since you're the author of that code, there are some things I would like to > ask you about rcube_ldap.php. Well, others had implemented a lot of functions as well. I'm not very experienced with LDAP even if my name is found in that file. > > I'm copy-pasting the original message I sent to that list: > > > --- > 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. Correct. What do you wanna use it for? > > 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? No. > 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? I don't unferstand what you intend to do with LDAP and therefore I cannot answer that question. ~Thomas _______________________________________________ List info: http://lists.roundcube.net/dev/
