[Date Prev][Date Next]
RE: How can I lock a record using php-ldap?
Your second point is a good one and one that I overlooked. It's
relevancy would be in direct proportion to the expected load on the
server relative to the server's performance capabilities, though. And
the convenience and simplicity of storing all such data in the directory
and using common access mechanisms may outweigh the storage load up to a
certain load point, don't you think? Provided, of course, that you can
solve the locking problem which has been feasably done in a couple other
responses (e.g., Alan Sparks's SINGLE-VALUE technique). And keeping in
mind that all the aforementioned locking mechanisms will add even more
overhead to your directory server, a condition which should be taken
From: Jon Roberts [mailto:email@example.com]
Sent: Wednesday, January 22, 2003 9:37 AM
To: Mike Denka
Cc: OpenLDAP Software
Subject: Re: How can I lock a record using php-ldap?
Mike Denka wrote:
>Jim C wrote:
>>. . and I definitely don't recommend storing
>>the highest uidNumber value in the directory database itself.
>Why not? Aside from the fact that it is difficult to lock, are there
Because 1) it's difficult to lock and 2) time to update will be slower
than memory or even accessing a flat file. If you're adding a lot of new
entries, you'd be simultaneously updating this other entry for each
one, essentially doubling your load on the directory server. Don't
forget: add/update entry => update indices.