|
>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 8/9/00 5:46:58 PM
>>>
>>The other has to do with extended operations that need to report error conditions that are not currently defined. For example, say there's an extended operation that starts the replication process, an error may need to be returned that states that the replication agreement is not defined correctly. In this case, none of the existing LDAP resultCodes can sufficiently communicate the problem. I propose that each extension define its own error reporting mechanism (if appropriate), and we either create yet another result code called extendedOperationError, or just use other to signal that one should look at the results of the extended operation. >> >>Any other ideas? > >I suggest the specification defining the extended operation define >additional resultCodes as needed. Are you suggesting that the new result codes be returned in the resultCode
field of the LDAPResult, or that the extended response provide an alternate
field to report them? The former method won't work with 2251 (4.1.10,
"If a client receives a result code which is not listed above..."). We could
easily fix this in the bis doc.
|