On Fri, 22 Feb 2002, GOMEZ Henri wrote: > The only problem with jk2 is that it's only available > for Apache 2.0, port to Apache 1.3 should be conducted...
True. My focus was on cleaning up the code, and it was much easier with a single server. I don't think updating the other servers is very difficult. > And for sure IIS/iPlanet, and we have to know if we > could have a mod_jk 2.x with and without APR (with > less features) Is APR released as 1.0 ? Do we gain anything by removing the current jk_pool, jk_map, etc ? Have we tested APR with IIS ? IMHO - jk2.0 should keep the old code and be able to operate without APR ( but default to APR ). In 2.1 we can drop the old code and use APR exclusively. The current design allows one to use 'native' APIs - if a server has a pool-equivalent it can be used ( so in Apache1.3 we have the choice between 1.3 pool, apr pool, or jk pool ). Same for logging, maps. Long term I think it would be good to use the 'natives' whenever possible, and APR for missing features. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
