[Date Prev][Date Next]
Re: bind fallback
On Mon, 28 Aug 2006 17:58:38 +0200 (CEST)
"Pierangelo Masarati" <firstname.lastname@example.org> wrote:
> >> deprecated), and it's intended to be the opposite of ldap_initialize(3)
> >> (formerly, ldap_init(3), now deprecated). The name might sound
> >> misleading; it comes from draft-ietf-ldapext-ldap-c-api.
> > Funny the latest draft-ietf-ldapext-ldap-c-api-xxx.txt from webcvs has
> > no mention of ldap_initialize(3). Is this really portable? Are these
> > functions ok to use with 2.2?
> Yes. The draft is very old and its design is a bit outdated. OpenLDAP
> implements the calls in the draft, but most of them are deprecated in 2.3
> and may no longer be supported in the future. OpenLDAP provides valid
> alternatives to deprecated code. Anything but ldap_initialize() should be
> used to initialize a connection, for example. It has been around for a
> long time (2.something, possibly 2.0). I don't know about portability
> with respect to other implementors (and I don't want to).
So what you're saying is that OpenLDAP will not be following industry
accepted standard APIs and may even remove functionality wrt those
> In general, fixing memory leaks in obsolete code sounds like a waste of