The C LDAP Application Program Interface
draft-ietf-ldapext-ldap-c-api-05

Document Type Expired Internet-Draft (ldapext WG)
Authors Mark Smith  , Tim Howes  , Andrew Herron  , Mark Wahl  , Anoop Anantha 
Last updated 2000-11-22
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-ldapext-ldap-c-api-05.txt

Abstract

This document defines a C language application program interface (API) to the Lightweight Directory Access Protocol (LDAP). This document replaces the previous definition of this API, defined in RFC 1823, updating it to include support for features found in version 3 of the LDAP protocol. New extended operation functions were added to support LDAPv3 features such as controls. In addition, other LDAP API changes were made to support information hiding and thread safety. The C LDAP API is designed to be powerful, yet simple to use. It defines compatible synchronous and asynchronous interfaces to LDAP to suit a wide variety of applications. This document gives a brief overview of the LDAP model, then an overview of how the API is used by an applica- tion program to obtain LDAP information. The API calls are described in detail, followed by appendices that provide example code demonstrating use of the API, the namespace consumed by the API, a summary of require- ments for API extensions, known incompatibilities with RFC 1823, and a list of changes made since the last revision of this document.

Authors

Mark Smith (mcs@netscape.com)
Tim Howes (timhowes@yahoo.com)
Andrew Herron (andyhe@microsoft.com)
Mark Wahl (mark.wahl@informed-control.com)
Anoop Anantha (anoopa@microsoft.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)