On 2/11/10 6:03 PM, Kiran Ayyagari wrote:
hi guys,
Here is a summary about the delete operation handled by various
client SDKs
jLdap :
-------
synchronous :
* delete(String dn)
* delete(String dn, LDAPConstraints cons)
asynchronous :
* delete(String dn, LDAPResponseQueue queue)
* delete(String dn, LDAPResponseQueue queue, LDAPConstraints cons)
UID :
-----
synchronous :
* delete(String dn)
* delete(DeleteRequest deleteRequest)
* delete(ReadOnlyDeleteRequest deleteRequest)
asynchronous :
* asyncDelete(DeleteRequest deleteRequest, AsyncResultListener
resultListener)
* asyncDelete(ReadOnlyDeleteRequest deleteRequest, AsyncResultListener
resultListener)
ODS :
-----
synchronous :
* delete(DeleteRequest request)
* delete(String name)
asynchronous :
* delete(DeleteRequest request, ResultHandler<Result> handler)
JNDI :
------
this is completely a different beast to tame ;)
* Context.unbind()
* Context.destroySubcontext()
The proposed API for delete operation in ADS is
ADS :
-----
synchronous :
* delete( String dn )
* delete( LdapDN dn )
* delete( DeleteRequest delRequest )
asynchronous
* deleteAsync( String dn )
* deleteAsync( LdapDN dn )
* deleteAsync( DeleteRequest delRequest )
thoughts?
Sounds good. as usual, this is not the ADS proposal (we currently don't
have the deleteAsync methods), but what we think is ok from the user
POV. ADS has taken anther road atm (but will move forward and change
what is currenttly done).
--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com
