[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Locking/atomicity in OpenLDAP

To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Locking/atomicity in OpenLDAP
From: Vetle Roeim <vetle@opera.com>
Date: 08 Jan 2001 08:49:51 +0100
Cc: Matthew Palmer <mjp16@ieee.uow.edu.au>, openldap-general@OpenLDAP.org
In-reply-to: <5.0.2.1.0.20010107192455.00a60170@router.boolean.net>
Organization: Opera Software AS
Original-sender: vetler@ifi.uio.no
References: <5.0.2.1.0.20010107192455.00a60170@router.boolean.net>
User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7

* Kurt D. Zeilenga
> At 12:41 PM 1/8/01 +1100, Matthew Palmer wrote:
> >What are the general atomicity guidelines in OpenLDAP?
> 
> The atomicity guidelines of LDAP should apply.
> 
> In general (*), LDAP provides atomicity at the entry level.
> That is, any two operations acting upon a entry are serialized
> by the server.

What about transactions? I guess LDAP doesn't support this (found no
reference to it in RFC 2251), but I could imagine situations where it
could be very useful.

Would transactions in LDAP be a good idea?

vr

Follow-Ups:
- Re: Locking/atomicity in OpenLDAP
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

References:
- Re: Locking/atomicity in OpenLDAP
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

Prev by Date: Re: modify DNs in PHP
Next by Date: ldap_modrdn()/ldap_modrdn2()
Index(es):
- Chronological
- Thread