Viewing Software Enhancements/4033
Full headers

Major security issue: yes  no

Notes:
patch welcomed
Notification:

Date: Fri, 16 Sep 2005 07:24:01 GMT
From: rravi@novell.com
To: openldap-its@OpenLDAP.org
Subject: Enhancement requests :  Need LDIF parsing API's 

Full_Name: RAVI CR
Version: Current
OS: LINUX
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (202.144.95.244)


Feature requests :  Need LDIF parsing API's 
Developers want  to use  these  API's in their application for parsing the LDIF
files.

Present LDIF API's: 
The API's only provides lexical analysis part of LDIF handing and not the actual
LDIF parsing.  The routines only handle line continuations and breaking lines
around the colon.  They do not parse LDIF elements, such as an
ldif-attrval-record or ldif-change-record, into C structures.  The caller of
these routines is expected to do that parsing. (For EG :    ldapmodify.c  code 
handles the LDIF parsing).

Requirement: 
A high-level LDIF API Set should be designed and implemented as a library. This
API would define C structures for LDIF elements such as ldif-attrval-record and
ldif-change-record, and provide facilities for translating them to LDAPMod
structures.

Followup 1

Date: Mon, 04 Jan 2010 14:09:14 -0700
From: Rich Megginson <rmeggins@redhat.com>
To: openldap-its@OpenLDAP.org
CC: rravi@novell.com
Subject: Re: (ITS#4033) Enhancement requests :  Need LDIF parsing API's

See also 
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=6194;selectid=6194

An API that returned LDAPMod ** and LDAPControl ** would be sufficient 
for all cases, including the LDAP ADD and any LDAP modify cases.  The 
current discussion revolves around exposing the high level LDAPMod and 
LDAPControl APIs to the lower level libldif, or just passing the parsed 
values as lists of struct berval *