apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: [PATCH] LDAP extension to apr-util (take 2)
Date Mon, 13 Aug 2001 20:12:52 GMT
Ryan Bloom wrote:

> There are already multiple LDAP libraries, what are we trying to solve by putting
> an abstraction layer into APR?  Are we sure that the problem needs to be solved,
> or are we doing work just to do work?

There are multiple LDAP libraries - which is exactly why the LDAP
library was abstracted. There is the "standard" way of doing things,
then there is the "netscape" way of doing things, which has just changed
again to the "iplanet" way of doing things - then throw in the two
different ways of doing SSL/TLS (netscape|standard) - linking against an
LDAP library is a real pain in the ass.

Then there is the idea that we don't want to
connect/bind/query/unbind/disconnect many times per connection (which
happens if auth_ldap and keepalives are used together) or if auth_ldap
and the LDAP-proxy backend are used together - thus the caching and
connection reuse abstraction layer to do this.

At all times the core LDAP library is available should the application
want to use it. The LDAP layer is an addition to rather than an
interface to LDAP. The code for the layer was sourced from an existing
Apache module - auth_ldap, which has been around for quite a while and
is stable.

minfrin@sharp.fm		"There's a moon
					over Bourbon Street
View raw message