An approach to enable directory transactions
draft-shivkumar-ldapext-dirtxn-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | |||
| Last updated | 2000-08-07 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The directory is becoming an important part of the organization. As the data in the directory becomes more critical, it needs to be consistent. With more applications storing information in the directory, there is a need for transaction (atomic commit/rollback) services to be offered by the directory to ensure consistency. This document describes a mechanism to implement transaction service in a distributed replicated directory. It also describes the LDAP APIs that can be used to provide a standard interface for the transaction service.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)