Mladen Turk wrote:
<AjpWorker and <AjpBalancer for example, or do we need to mimic that inside the existing configuration directives? Well the, <AjpWorker can be mapped to ProxyRemote if you change it to <ProxyRemote. See my point?
AjpBalancer could be applied to a theoretical proxy_balancer module (all modules can define their own config parameters, even the helper modules, the only guideline is that the config directives are named to give some indication of the scope they're valid for, so instead of a directive called "Fred" which doesn't mean anything to anybody, it should be "ProxyAjpFred").
What does AjpWorker do? (Is there docs for mod_jk anywhere, when I last looked I could not find any).
There is also a lot of extra params that we'll need to set for each particular worker or Remote.
If you are will to support something like that, then we can speak on.
Quite willing - the extra params can be defined as valid for the proxy_ajp module only, or extra general parameters can be added to the proxy framework.
The idea is that if some feature has general application to all the modules (such as load balancing) then the change should be made to proxy and be applied system wide.
Me neither. I really see no reason for that, except that we don't have neither proxy_ajp nor proxy_loadbalancer. I also see no reason why the mod_proxy functionally cannot be implemented in mod_jk2 :).
Because of end user expectation. mod_proxy is currently the "shipped with Apache" option for backend protocol support. If suddenly mod_proxy and friends were turfed out and replaced with an entirely different module and different set of directives, people's reaction would be "huh?".
Look, if others on the tomcat-dev are willing to write the proxy_ajp and proxy_loadbalancer, then OK. After all, I'm Borg, I will adapt :). I personally don't like the idea, and still think that we should first make something workable outside the Apache2 tree, at least for the reason to be able to make a release without waiting for the rest of the guys.
Would it be possible to copy the entire mod_proxy inside j-t-c tree and then later merge it with the httpd tree when we reach some version 1.0?
You could do that - although if you make changes to mod_proxy itself (which you very likely will have to do to support some of the stuff, like the adding of new hooks, etc) it would be best if these were posted as they happened to the [EMAIL PROTECTED] list, then they could be applied to httpd v2.1-dev, with potential backports going to v2.0.
Doing this in bite sized pieces as needed would be a lot easier to review than a single big merge at the end, although keeping a local copy for yourselves to try things out first will also make your lives easier.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
