Thanks Kiran for the taking. >> I am implementing a Mavibot based backend*. Would you clarify a bit about this? I'm wondering if it's the same thing, the on-going LdapIdentityBackend Yaning is working on? Or you mean something that uses Mavibot directly instead of by the LDAP connection API?
>> Is there any reason why the API methods start with doXXX()? I would think AbstractIdentityBackend isn't the interface, and the doXXX() methods are not the APIs. Please see the APIs in the interface IdentityBackend/IdentityService. AbstractIdentityBackend is a common abstract class to implement the API interface, and provides some useful functionalities like cache. I thought if you don't like it, you could start with totally new, implementing IdentityBackend/IdentityService directly. >> now is the time after today's commits in Mavibot trunk that address these >> bugs. Glad it's the time now. It will help a lot. Regards, Kai -----Original Message----- From: Kiran Ayyagari [mailto:[email protected]] Sent: Monday, June 29, 2015 5:43 PM To: [email protected] Subject: [backend] AbstractIdentityBackend interface I am implementing a Mavibot based backend*. Is there any reason why the API methods start with doXXX()? This looks a bit odd and hard to read. I would like to strip the 'do' verb from these methods, please let me know if there are any objections. * this is on hold for a long time due to the free page management bugs, but now is the time after today's commits in Mavibot trunk that address these bugs. -- Kiran Ayyagari http://keydap.com
