Mladen Turk wrote:
Some rationale:
I spoke with Henri and we decided that although mod_proxy with proxy_ajp is a good idea (in the long term... very long term), we need something that will fill in the gaps.
As there is an existing codebase, getting a module together that supports Apache v2.0 natively is a good start to clean up the module and get it aligned with how Apache v2.0 works.
I however will be -1 on the eventual formal inclusion of the module into httpd natively until it supports the proxy framework. A significant amount of work has been done in httpd to ensure that proxy functionality (such as cache) is available to as wide an audience of users as possible. Adding a module that neither conforms to the established framework inside httpd, or offers it's functionality to protocols outside of AJP I believe is a step backwards for httpd.
That being said, all work on mod_ajp to get it aligned with httpd v2.0 is a step in the right direction as it makes it easier in the long term to create separate modules for features such as load balancing, etc, and eventually get the module aligned so that it fits into the mod_proxy framework.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
