I also agree. However, there may be issues related to replication, whether LDUP or proprietary, that may affect an LDAP server's overall efficiciency for intense writes. For instance: replication delay adds an additional delay between the time an entry is updated and the time that update becomes fully visible.
James A Benedict
Advisor, IP Directory Systems Architecture
Preside Policy Services
NORTEL NETWORKS
Ph: (613) 763-3909
> -----Original Message-----
> From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
> Sent: Wednesday, June 07, 2000 11:11 AM
> To: Rich Salz
> Cc: Martin.Rahm@nokia.com; ietf-ldapext@netscape.com
> Subject: Re: Intense LDAP write operations
>
>
> At 10:08 AM 6/7/00 -0400, Rich Salz wrote:
> >> One concern I have is that LDAP is supposed to be less efficient
> >> when it comes to intense write operations.
> >
> >There is nothing intrinsic to the LDAP specifications that
> make writes less
> >efficient.
>
> I concur. However, LDAP does not offer a number of other
> features, such as client/server transactions, which might
> be needed.
>
> When folks start talking about intense write operations,
> I generally refer them to Tim Howes' article "LDAP: Use
> as Directed" <http://www.data.com/issue/990207/ldap.html>.
> "LDAP isn't a replacement for relational databases
> (and never will be)."
>
> Kurt
>
>