On Mon, Aug 13, 2001 at 03:59:08PM -0500, William A. Rowe, Jr. wrote: > apr-util should be stable right out the door ... is this ldap code likely to > evolve significantly over time?
Probably not. I doubt there is much more work to be done for the LDAP code. It is a fairly thin layer (although it isn't as thin as I'd like it, but that's me). As I see it, the problem is that if we add any features in httpd that require LDAP (mod_auth_ldap, httpd configuration via LDAP), you now need to check out apr-ldap. Yuck. Based on the way Ryan tells it, apr-util should be the kitchen sink of things that don't belong in apr or in httpd. I think we agree it doesn't belong in APR as it is not adding core portability features. I don't think it belongs in httpd as I could definitely use such code in other projects not associated with httpd. apr-util seems the most logical place, IMHO. -- justin
