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

Re: Openldap ldbm cache corruption

To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Openldap ldbm cache corruption
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Date: Wed, 13 Jan 1999 09:51:27 +0100
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <3.0.5.32.19990112181343.00954c00@localhost>
References: <3.0.2.32.19990113015812.00f83240@dokka.maxware.no> <3.0.5.32.19990112162851.00950ea0@localhost> <F28436604B38D111BAE100805F0DE17D6E034A@arsenic>

Thanks for the response - I'm looking forward to the time when OpenLDAP
starts implementing LDAPv3 and UTF-8.

Charsets are about the biggest bogosity in present LDAPv2 deployment,
with the 8859-1/UTF-8/T61 botch of Microsoft/Netscape/Standard,
so it would be great if the open reference implementation did UTF-8 properly.

And it ain't simple.....

                Harald A

-- 
Harald Tveit Alvestrand, Maxware, Norway
Harald.Alvestrand@maxware.no

References:
- Re: Openldap ldbm cache corruption
  - From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
- Re: Openldap ldbm cache corruption
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Openldap ldbm cache corruption
  - From: Robert Rothlisberger <rwroth@netdox.com>
- Re: Openldap ldbm cache corruption
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

Prev by Date: RE: back-passwd issues
Next by Date: permissions on slapd.conf
Index(es):
- Chronological
- Thread