[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: I-D ACTION:draft-ietf-ldapext-ldapv3-dupent-02.txt

To: ietf-ldapext@netscape.com, Thomas.Salter@unisys.com
Subject: RE: I-D ACTION:draft-ietf-ldapext-ldapv3-dupent-02.txt
From: Jim Sermersheim <JimSe@novell.com>
Date: Mon, 18 Oct 1999 10:25:53 -0600
Content-disposition: inline
Resent-date: Mon, 18 Oct 1999 09:34:17 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"2mxZ3B.A.ihD.Vv0C4"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

Right, I included those errors for cases where a search may succeed, but the use of the control causes a failure. I tried to limit the error types to those that could be caused by servicing the control.  I believe the server side sort and virtual list view controls do this as well.

Jim

>>> "Salter, Thomas A" <Thomas.Salter@unisys.com> 10/18/99 08:17AM >>>
Why does this control define its own error results?  Can't these error
conditions all be handled in the error result of the search operation?  If
not, how do the two error conditions interact?  Is it possible for the
search to succeed, but the control to fail?

Prev by Date: RE: I-D ACTION:draft-ietf-ldapext-ldapv3-dupent-02.txt
Next by Date: RE: grant / deny precedence indraft-ietf-ldapext-acl-model-04.txt
Index(es):
- Chronological
- Thread