On Tue, Aug 27, 2002 at 05:25:25PM -0700, Greg Stein wrote: > It would seem that changes to the directives would be easy, and we could > also deprecate older directives. In all cases, we'd change our .conf files > and the doc, issue warnings for old usage, and then just "wait a while" > before removing old support.
The real problem is with mod_auth_dbm. Part of the problem is that mod_auth_dbm is dependent on the new mod_auth_basic. I guess we could force mod_auth_dbm to build mod_auth_basic via config.m4 magic. (mod_auth would be removed entirely, so that might be iffy too.) Yet, I'm not clear how we could trick mod_auth_basic to use DBM unless they add "AuthProvider dbm" to mimic the old mod_auth_dbm code. (The catch is that mod_auth_basic should use 'file' as the default provider to mimic the no longer present mod_auth.) Hmm. One thought would be to implement the multiple provider scheme John mentioned and always do file/dbm unless said so. But, ick, that might catch people by surprise and I'm not sure if that is really possible as mod_auth_dbm and mod_auth used to share the same config syntax (ick!), so I'm unclear what would happen when both would try to interpret things. Ick, ick, ick. Thoughts? -- justin
