Graham Leggett wrote: > > Well, the development will not be over in 2 days, and the > plan is to > > use mod_ajp as a base for testing new protocol extensions, > and to be > > always a little bit faster and better then mod_proxy with > proxy_ajp :). > > Don't forget mod_proxy is just a framework - there would be > no "faster than proxy_ajp" because prioxy_ajp would be > mod_ajp with config directives arranged differently. >
True, but we will still have a framework that existing jk/jk2 will find easy to handle. It will also be a framework for testing protocols and protocol layers, and we will not need to wait for a official release for bugfixes. Once when proxy_ajp will be operational and stable we will move mod_ajp to other direction probably adding jmx and autodiscovery, that is mostly TC related and dependant, so the work will not be wasted, thought, with possible support for inclusion in proxy_ajp :). > > > The mod_proxy itself will have to face a lot of extra work too. > > Exactly - which is why I'm dead keen to have the AJP work > aligned with proxy, so that proxy can benefit from AJP > features like load balancing, etc. > Sure, we will work on proxy (I can speak only for myself), but... Well, except j-f-c none of us has a commit privilege to httpd tree, so how do you suppose that the development can take a place after all? > > > > If you succeed to build such a feature for mod_proxy and http > > protocol, then we will already have a ready proxy_ajp > protocol extension. > > From the sounds of things, many of these features exist (or will soon > exist) in mod_ajp. Moving or copying these features out of > mod_ajp and into either mod_proxy* or any of the core modules > isn't a difficult thing to do. If you create patches that you > need for either proxy or the core to support stuff that you > need, I'll make sure they get into httpd > v2.1 with support for inclusion into httpd v2.0. > Cool, The first thing I will do is a extendable scoreboard, so that the module can exchange params among child process. The loadbalancer will use that to calculate the scores for each lb instance. I rewrote a workable solution for that in jk2 using apr, so it shouldn't be a big deal. Exactly the same scoreboard will be in mod_ajp, so once you commit something to 2.1 core, we will drop our own. MT.
smime.p7s
Description: S/MIME cryptographic signature
