>> Ok, I'd like to have mod_jk 2.x with Apache 1.3 and >> may be with/without APR... > >I start to have doubts about supporting mod_jk2 without >APR - we should keep doing that at least until APR is >officially released and until we have a working >mod_jk2 for IIS/etc using APR. After that we can >deprecate/remove the duplicated code ( pool, map). > >> >( you don't need to send diffs, just check in and if >> >there are problems we'll fix them ). >> >> What about renaming mod_jk.c in native2 to mod_jk2.c > >If you talk about the module name - I think that's >absolutely required.
mv mod_jk.c mod_jk2.c, ok ? >This is a very good solution for backward compatiblity - >keep the old code around, it's the most backward >compatible, and gradually move to the new one >( driven by new features like faster channels, >etc ) > >That requires making both versions 'coexist', and >that requires renaming the module and the conflicting >directives. Done, I'll modify mod_jk.c to mod_jk2.c ASAP -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>