Hello dear wise guys :-)
Is there any nice feature at Oo-LDAP implemented to get the information if an object is changed; something like a internal version number...???
We would like to use LDAP for storing complex configuration data which can have dependencies. For that a version number for all objects is necessary. Unfortunately these changes must be done also in a safe way which means that a version change must be done in a “atomic operation”. A internal incrementing by the LDAP server seemed to me a quite more simple solution than to try this to handle via the ( say here ~ 6000 concurrent ) clients.
By the way: Do anyone implement something like a LDAP server based sequence number which can be queried???
Thanks a lot for your hints... and best regards Karsten (Sorry for the bad English ;-()
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other then the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
Is there any nice feature at Oo-LDAP implemented to get the information if an object is changed; something like a internal version number...???
Yes, see entryCSN, especially in conjunction with entryUUID.
Do anyone implement something like a LDAP server based sequence number which can be queried???
Yes, see contextCSN at the top of the suffix, as provided by slapo- syncprov.
If you need your app to watch changes as they happen, it might be wise to implement the syncrepl protocol (RFC 4533).
Matthew Backes Symas Corporation mbackes@symas.com
openldap-technical@openldap.org