Henri Gomez wrote:
Of course, I want a module designed for Apache 2.x (2.0/2.1). Apache 1.3 could live with jk 1.2.x. IIS/NES/DOMINO could use jk 1.2 or jk2. No more code complexity to handle all the web-servers around, we should focus on Apache 2.x.
Yes. A lot of the complexity is to allow running with many servers, having custom configuration, etc. Apache 2 is now (finally) getting significant deployments numbers, and is bundled in many distributions, so adding special support for it makes sense (as long as we can distribute our module in their codebase, otherwise it's less interesting).
For example majors Linux distributions are now using Apache 2 instead of Apache 1.3. So Apache 2.x will be more and more used.
When not running inside Apache, there are tons of things when cannot use, including configuration. So the best is indeed to keep JK around for supporting other servers. One of the big problems is that it would be best to keep developing either jk 1.2.x or jk 2.0.x, but not both ;)
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
