It would be best to use the version of APR which is distributed with the current Apache 2 release so that there are no conflicts when using mod_jk with Apache 2.
Requiring APR would allow using a global connection pool for the socket connections to Tomcat. And allow more sophisticated load balancing when you can have access to global information about how each pool of connectors to Tomcat is performing.
If this involves significant changes to the code we might want to bump the major version to jk3.
We will still need at least one more release of mod_jk 1.2 for the minor changes committed since the 1.2.5 release.
Regards,
Glenn
Henri Gomez wrote:
Hi to all,
Now that jk seems stabilized a bit, should we focalize on jk2 ?
For instance I added some features to jk (ping/pong) which should be ported to jk2.
Also I wonder if APR is mandatory for jk2.
I'd like to use APR as a facade to all Operating System calls.
The goal is to hide all the complexity of Windows, iSeries, differents Unix implementations behind APR which is now stable and well diffused.
As such it will be +1 to make APR mandatory and start modifying jk2, to make it use only APR call.
But I'd like to have your opinion first.
PS: For those of you who was here 2 or 3 years ago, the requirement of APR for mod_webapp got my total -1 at this time since it wasn't really available, but today that's completly different.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
