It would probably make sense to broadcast a list of improvements, etc,
when 1.2.18 is released at least...
Henri Gomez wrote:
2006/7/18, Jim Jagielski <[EMAIL PROTECTED]>:
On Jul 14, 2006, at 10:34 AM, Jess Holle wrote:
> What is the plan for mod_proxy_ajp catching up with all the
> improvem
2006/7/18, Jim Jagielski <[EMAIL PROTECTED]>:
On Jul 14, 2006, at 10:34 AM, Jess Holle wrote:
> What is the plan for mod_proxy_ajp catching up with all the
> improvements in the latest mod_jk?
>
> As I understand it, mod_proxy_ajp is currently lagging, which is
> understandable -- one or the ot
On Jul 14, 2006, at 10:34 AM, Jess Holle wrote:
What is the plan for mod_proxy_ajp catching up with all the
improvements in the latest mod_jk?
As I understand it, mod_proxy_ajp is currently lagging, which is
understandable -- one or the other has to. I'm just wanting to get
some grasp o
Rainer Jung wrote:
I think Mladen and I both want people to move to mod_proxy_*. Mladen
already offered help and httpd-dev for porting mod_jk improvements to
mod_proxy_* and I definitely want to join him in that. But first I need
to manage the pending mod_jk release, something we are right now do
I think Mladen and I both want people to move to mod_proxy_*. Mladen
already offered help and httpd-dev for porting mod_jk improvements to
mod_proxy_* and I definitely want to join him in that. But first I need
to manage the pending mod_jk release, something we are right now doing.
I don't know mo
What is the plan for mod_proxy_ajp catching up with all the improvements
in the latest mod_jk?
As I understand it, mod_proxy_ajp is currently lagging, which is
understandable -- one or the other has to. I'm just wanting to get some
grasp of the probable/planned timeframe for mod_proxy_ajp cat
