Hello mr. Pierangelo Masarati, Thanks for the reply. But, is move subtree operation (implemented in openldap server side) is a combination of delete subtree and add right?
Or is it like changing the references in the dn2id file? Thanks in advance, Arunachalam. **************************************************************************** **************************** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! -----Original Message----- From: Pierangelo Masarati [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 07, 2007 3:28 PM To: [EMAIL PROTECTED] Cc: [email protected] Subject: Re: Deleting subtree - server side Arunachalam Parthasarathy wrote: > Hello, > > Can I know the reason why it is not implemented? Yes. Basically, it's an operation that is not atomic in pure LDAP (namely, it requires more than a write operation), and thus it could be implemented in many different ways (I mean: handling errors and conflicts in many different ways). So there should be: 1) a need for it 2) an agreed specification about how to do it 3) someone who codes it. I recall seeing some old specification (e.g. <draft-armijo-ldap-treedelete>, expired 2001). A much better approach would be to use LDAP transactions (e.g. <draft-zeilenga-ldap-txn>) so that the operation either fails or succeeds atomically. In OpenLDAP there's experimental support for transactions, but I'm not sure subtree deletion can be performed right now. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: [EMAIL PROTECTED] ---------------------------------------
