[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
LDAP Schema
Hi everybody,
I have some questions regarding Schema updatation.
1. How do I update an objectclass defination of an userdefined
objectclass through client API? I am able to create and delete an
operation. But for updation, with current LDAP client implementation, I
have to delete and recreate the objectclass to incorpoate the changes.
Problem with this approach is that if some failure occurs after
objectclass deletion, the DSA schema will be in unstable state. I am
looking solution that can modify the objectclass definition in an atomic
operation.
2. why it is neccessay to specify entire objectclass hierarchy as the
value for the attribute 'objectclass' for a directory?. (If I don't
specify, entry will not be fetched in case filter is set to, say
"objectclass=top".)
K.Senthil Kumar.
CA -TCG Software.
Disposition-notification-to: k.richardson@man05t1.wins.icl.co.uk
Received: from threadgill.austin.innosoft.com ([207.8.108.5])
by INNOSOFT.COM (PMDF V5.2-29 #30494)
with ESMTP id <01J43XP4B9TQ94F9SS@INNOSOFT.COM> for
ldapext-archive@pipe.thor.innosoft.com; Fri, 13 Nov 1998 02:36:30 PST
Received: from glacier.mcom.com (h-205-217-233-39.netscape.com)
by austin.innosoft.com (PMDF V5.1-10 #13579)
with ESMTP id <0F2C007AYW4TUR@austin.innosoft.com> for
ldapext-archive@pipe.thor.innosoft.com; Fri, 13 Nov 1998 04:36:29 -0600 (CST)
Received: (from list@localhost) by glacier.mcom.com (8.7.3/8.7.3)
id CAA15353; Fri, 13 Nov 1998 02:13:37 -0800 (PST)
Resent-date: Fri, 13 Nov 1998 02:13:37 -0800 (PST)
Date: Fri, 13 Nov 1998 10:06:00 +0000
Resent-from: ietf-ldapext@netscape.com
From: Richardson K <k.richardson@man05t1.wins.icl.co.uk>
Subject: Status of LDIF and Changelog?
Resent-sender: ietf-ldapext-request@netscape.com
To: ietf-ldapext@netscape.com
Resent-message-id: <"P8MNp.0.ql3.FP0Js"@glacier>
Message-id: <JA8AAAAAAJ8rPwABYQACiMOLwb9U@man05t1.wg.icl.co.uk>
MIME-version: 1.0
X-Mailer: TeamWARE Connector for MIME
Content-type: text/plain; charset=iso-8859-1
Content-disposition: inline
Content-transfer-encoding: quoted-printable
Precedence: list
X-Loop: ietf-ldapext@netscape.com
X-Map-MIXER-Originators: false
Envelope-ID: JA8AAAAAAJ8rPwABYQACiMOLwb9U@man05t1.wg.icl.co.uk
X-Mailing-List: <ietf-ldapext@netscape.com> archive/latest/1001
Hi,
I have some general LDIF-related questions. The current LDIF
technical specification (draft-good-ldap-ldif-01.txt) is now an
individual contribution although it was previously an ASID work
item. Presumably this is now destined to be an informational RFC=3F
If so, shouldn't we be considering giving LDIF a more formal
status than this=3F All of the LDAP servers I know support LDIF to
some degree and it seems to me that it would better if the
format used to import/export and apply changes to different
servers was an agreed standard - interoperability between servers
goes beyond the basic protocol level.
I guess if the LDIF status were to reviewed then the LDIF
extensions needed to meet certain country's legal/regulatory
directory requirements (draft-andersen-isss-ws-dir-ldifext-00.txt)
would also need to be considered - possibly for optional
implementation on top of a "standard" LDIF=3F
Also, the changelog draft (draft-good-ldap-changelog-00.txt)
which exploits LDIF expired on October 1st. Is a new draft planned
or is the changelog proposal now considered to be superseded by the
planned LDUP replication mechanisms=3F
Keith Richardson
ICL, Manchester, UK