Rakesh Yadav wrote:
Actually i am using a DN
It is having a single attribute userId. And i want to use this attribute
for other entries of User
for an Example:
when a request for adding a information of any user comes that time i
read the value of userId and update this value by One
means now it is having value of userId
But between the process of reading and updating if some other request
also reads the value of userId: 5000 then both users have the same value.
But we don't want this.
so is there any mechanism through which we can hold the request,so it
dose not get the value of userId between the process of reading and
You told me in your reply:
"There are ways for applications to perform cooperative locking in LDAP"
Please tell me about locking.
There are dozens of similar posts in the archives; this topic has been covered
for several years...
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/