You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Jess Holle <je...@ptc.com> on 2006/07/14 16:34:59 UTC
mod_jk 1.2.17 vs. mod_proxy_ajp
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 catching up.
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk 1.2.17 vs. mod_proxy_ajp
Posted by Jess Holle <je...@ptc.com>.
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 doing.
>
Understood. That makes perfect sense.
> I don't know mod_proxy_* code good enough to make a precise statement
> about schedule for porting features, but I assume, that mod_proxy_* will
> be very close to mod_jk (if not better) around october.
>
Thanks. That sort of rough timeframe is very helpful -- even if is
slips by a couple of months.
> There are also plans by jfclere, Mladen and others to improve
> mod_proxy_* and possibly AJP much further than what mod_jk/AJP13 is able
> to do at the moment, but I'm sure this part is much more complicated and
> will take a couple of months.
That can wait -- as much as I'd like to see support for >8K headers!
--
Jess Holle
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk 1.2.17 vs. mod_proxy_ajp
Posted by Rainer Jung <ra...@kippdata.de>.
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 mod_proxy_* code good enough to make a precise statement
about schedule for porting features, but I assume, that mod_proxy_* will
be very close to mod_jk (if not better) around october.
There are also plans by jfclere, Mladen and others to improve
mod_proxy_* and possibly AJP much further than what mod_jk/AJP13 is able
to do at the moment, but I'm sure this part is much more complicated and
will take a couple of months.
This is only what I think about it.
Rainer
Jess Holle schrieb:
> 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 catching up.
>
> --
> Jess Holle
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk 1.2.17 vs. mod_proxy_ajp
Posted by Jess Holle <je...@ptc.com>.
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 <ji...@jagunet.com>:
>>
>> 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 of the probable/planned timeframe for mod_proxy_ajp
>> > catching up.
>> >
>>
>> Since most of the people working on the mod_proxy_*
>> stuff aren't also on the TC dev lists, it is hard for them
>> to know of the improvements, etc...
>
> :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk 1.2.17 vs. mod_proxy_ajp
Posted by Henri Gomez <he...@gmail.com>.
2006/7/18, Jim Jagielski <ji...@jagunet.com>:
>
> 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 of the probable/planned timeframe for mod_proxy_ajp
> > catching up.
> >
>
> Since most of the people working on the mod_proxy_*
> stuff aren't also on the TC dev lists, it is hard for them
> to know of the improvements, etc...
:)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: mod_jk 1.2.17 vs. mod_proxy_ajp
Posted by Jim Jagielski <ji...@jaguNET.com>.
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 of the probable/planned timeframe for mod_proxy_ajp
> catching up.
>
Since most of the people working on the mod_proxy_*
stuff aren't also on the TC dev lists, it is hard for them
to know of the improvements, etc...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org