Mladen Turk wrote:
I think that we forked from jk/jk2 to be able to write from the scratch the module that will do exactly _one_ and _only_one_ thing; and that is effectively communicate with TC server using ajp13+ protocol. So, my question is. Why do we need again some container to accomplish that?
Because the container already gives you an established configuration method, a standard set of documentation, and a standard expectation from end users on how it should work.
Remember the end goal of the exercise is to produce software which solves a real world need of end users. One of the biggest real world end user needs is "something simple and straightforward that lets me get the job done with the least amount of time wasted messing around".
As a user, I would ask "why is the config for mod_jk different for mod_proxy?", and in fact as a user that's the exact reason I don't bother to use mod_jk. The easiest way to make the config method for mod_proxy and mod_jk the same is to implement proxy_ajp.
There are just too many compromises that we need to take if building proxy_ajp, and I thought that we wish no compromises at all.
Compromises like what?
I see no reason why every single feature of mod_jk cannot be implemented in a proxy_ajp, or with the assitance of other potential modules with general application like proxy_loadbalancer.
If we don' t build a module that will do exactly what it's meant to be doing, well... Same story again, and I don't understand why one would wish to do that?
If someone wishes to make a proxy_ajp I don't have a problem with that, quite opposite, but I still wish to write (like initially said) the module that will only and only communicate to application server cluster, nothing less, nothing more.
This is the precise goal of the proxy framework.
mod_proxy_http communicates with an HTTP server, nothing less, nothing more. It doesn't cache, it doesn't do anything - that's the job of other httpd modules like mod_dir, mod_cache, etc. mod_proxy_ftp communicates with an FTP server, nothing less, nothing more. mod_proxy_ajp would communicate via AJP. Nothing less, nothing more.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
