For 2.0 auth_ldap and mod_ldap it will probably forever remain experimental. There have been a lot of changes that have gone into the 2.1 version that IMO allowed it to graduate from experimental to a standard module. Most of these patches will never be backported to 2.0. In fact Josh's patch will probably not be backported (although it is simple enough that it could be) simply because the two code bases have become so different that it is difficult to backport anything. In most cases a backport is actually a rewrite. For this reason, I am ++1 for any effort to get 2.1/2.2 to BETA and released. Even if the latest "Multiple AAA provider" discussion has to wait for 2.4. We need exposure for the new authnz_ldap and util_ldap modules as well as the new auth module structure itself.
Brad >>> [EMAIL PROTECTED] Thursday, March 10, 2005 7:24 AM >>> Paul Querna wrote: > Jess Holle wrote: > >> Rodent of Unusual Size wrote: >> >>> CURRENT VOTES: >>> >>> * Promote mod_ldap and mod_auth_ldap from experimental to >>> non experimental status. >>> +1: bnicholes, wrowe >>> +0: minfrin (wait till the last cache bugs are ironed out) >>> >>> >> I think we're pretty well there -- at least in 2.0.53 plus the recent >> patch from Josh Fenlason to cover the case when a shared cache file >> is not specified on a platform supporting shared memory. >> >> Thoughts? > > It was promoted in 2.1. Why change the status for 2.0.x? > No big reason. Though I believe a non-experimental status is accurate now, I can understand if no one wants to rearrange any sources in 2.0.x. I was just reviewing the 2.0 status and the quoted portion above made it sound like this was still under consideration for 2.0. -- Jess Holle
