On Sun, 27 Jun 2004 14:56:37 -0700, Paul Querna wrote: > I believe it is time to look seriously at what would compose a 2.2 > Stable Branch. There have been various threads in the past saying a 2.2 > stable branch is not far off, and with the impending of release of APR- > 1.0, we should turn our attention to HTTPd. > I'm all for this. There are many new features in the 2.1 tree that I definitely want to play with on a *stable* release. > > - LDAP Authentication > - Needs to use the AuthN/Z framework > - Caching Code needs Stabilization or Removal(see AAA Cache) > This is definitely something that needs to be updated. and will try to give a full attempt in the next few weeks to find time to rewrite this module for the authn/z framework.
> - Document any API Changes for Module Authors. > - We want to make this an 'easy' upgrade. - Most of the work IMHO is > APR 0.9 -> 1.0 > Documentation, what a novel idea. This is one of the major deficiencies of the current 2.0 release, little in developer documentation and examples. > - Make _private.h files for all functions that are not part of the > public API. > I like this one, This would make things clearer as to what should and should not be used in a module (I reference my own blunder of accessing ssl_lookup_vars directly instead of using the OPTIONAL_FUNCTION in my mod_log_sql module as an example) > - AAA Cache Framework > - Caching Method for all AuthN/Z backends would be nice - Possible > todo this *without* API Changes.(Could be done once 2.2 is > stable) > I feel this is a very important module to get working and stabilized. Especially for use with LDAP authentication. > Edward Rudd http://www.outoforder.cc/
