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

Re: HEADS UP: API error code changes

To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: HEADS UP: API error code changes
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Thu, 11 Dec 2003 13:37:45 +0100
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <6.0.0.22.0.20031211035502.041a4e98@127.0.0.1>
References: <6.0.0.22.0.20031210202629.02707108@127.0.0.1> <HBF.20031211vpt2@bombur.uio.no> <6.0.0.22.0.20031211035502.041a4e98@127.0.0.1>

Kurt D. Zeilenga writes:
>> Negative codes make me a bit nervous.  Why not use codes >= 16384, since
>> they are for private use according to rfc3383?
> 
> Because nothing prevents a server from returning those codes.

Good point.

-- 
Hallvard

References:
- HEADS UP: API error code changes
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: HEADS UP: API error code changes
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: HEADS UP: API error code changes
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

Prev by Date: Re: HEADS UP: API error code changes
Next by Date: Enhancement request to control the LDAP search depth per entry
Index(es):
- Chronological
- Thread