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

Re: [ldapext] [Fwd: LDAP C API gripes]

To: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>
Subject: Re: [ldapext] [Fwd: LDAP C API gripes]
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Wed, 21 Feb 2007 19:00:43 +0100
Cc: Ldapext <ldapext@ietf.org>
In-reply-to: <B035A687-4312-4741-A1B6-AC161522E51B@Isode.com>
References: <45D251C0.2050306@highlandsun.com> <45DC6997.5020906@highlandsun.com> <B035A687-4312-4741-A1B6-AC161522E51B@Isode.com>

Kurt Zeilenga writes:
> For instance, consider validation of a value of the uniqueMember
> attribute.  A server might say value x is bad.  The library might
> be able to say that the 1st AVA of the 2nd RDN of the DN component
> is invalid.

No reason a server couldn't say that too, in the diagnosticMessage
field.  OTOH a library can also provide detailed error info which
a program can parse.

-- 
Regards,
Hallvard

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

Follow-Ups:
- Re: [ldapext] [Fwd: LDAP C API gripes]
  - From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>

References:
- [ldapext] [Fwd: LDAP C API gripes]
  - From: Howard Chu <hyc@highlandsun.com>
- Re: [ldapext] [Fwd: LDAP C API gripes]
  - From: Howard Chu <hyc@highlandsun.com>
- Re: [ldapext] [Fwd: LDAP C API gripes]
  - From: Kurt Zeilenga <Kurt.Zeilenga@Isode.com>

Prev by Date: Re: [ldapext] [Fwd: LDAP C API gripes]
Next by Date: Re: [ldapext] [Fwd: LDAP C API gripes]
Index(es):
- Chronological
- Thread