On Fri, 6 Feb 1998, Alexei Kosut wrote: > Especially not if we need to rename all our functions (see other threads). > And there are a number of other parts of the Apache API that really need > to be rethought (can we say "configuration"?) Backwards compatibility with > 1.3, either for the API or the config language or anything else, has never > (in the year and a half we've been discussing it) been a high priority for > 2.0.
Well, I think now is probably the time to at least think about how we are going to support current modules in the 2.0 framework. I'm not suggesting we should bend over backwards to make everything 100% backward compatible, but that we should value the work that has been done by third-party module authors and not disregard their efforts. Forcing radical changes on module authors could devalue them and maybe hurt the prospects of them continuing to develop Apache API modules (and move them towards, say, ISAPI where no-compilation is necessary to use later versions of the server). Paul
