Oh and I do agree completely with Stefan's comments as well. Think of it also this way. The less surface area exposed by the API the less of an overhead it is to deal with things like deprecation etc.
I like this idea with the DeleteHelper.On Thu, Jul 23, 2009 at 4:55 AM, Stefan Seelmann <email@example.com> wrote:
Emmanuel Lecharny wrote:
> Alex Karasulu wrote:I think the main API shouldn't be overloaded with too much convenience
>> Hmmm if I want to delete a tree of entries then I will have no choice
>> but to
>> wrap my LdapDN in a DeleteRequest which I must now create, just to add
>> control to delete the subtree.
> Yes, true. IMO, your proposal (deleteTree) is probably better.
methods and should be close to the LDAP protocol. I also think the main
API should not implement such algorithms (if server supports
TreeDeleteControl use it, else search/delete recursively).
What about putting these helpful convenience methods to a Helper class?
DeleteHelper.deleteTree( LdapConnection, LdapDN )
DeleteHelper.deleteChildren( LdapConnection, LdapDN)
My 2 cents,