|
>>>> Michael Ströder <michael@stroeder.com> 11/8/04 3:15:25 AM >>>
>Jim Sermersheim wrote: >> >> It's difficult (well, impossible I guess) to write an LDIF file which >> can be used to update schema because one never knows the name of the >> subschema subentry in effect for the object(s) for which the schema >> is being updated. (I'm assuming a DSA which can modify schema. i.e. >> X.501(93) Clause 14.5). > >There's not a single sub schema sub entry. In fact there could be many. >=> you have to know something a priory about the DSA before updating one >of its sub schema sub entries. Exactly (thus the "in effect for the object(s)" bit). This is why I'm wondering about a mechanism to (apriori) gather the knowledge needed to update the schema which the application intends to update.
>> Is there any effort underway to do something like this? > >Frankly I don't believe it's worth to think about something like this >any further. If you modify something like the sub schema via LDAP you >already implemented kind of a LDAP client and pointed it to a specific >server. I apparently worded my message poorly. My intent is to NOT have to implement anything other than an LDIF file.
>Ciao, Michael. Jim
|
_______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www1.ietf.org/mailman/listinfo/ldapext