AJP 1.5 should support automatic discovery of tomcat backend, new
systems and new webapps.
That's the current need for many of us when adding tomcats / webapp
behind Apache 2 webservers. In such case we need to restart them and
it's sad.
How could it be accomplished, may be via a master tomcat
Mladen Turk wrote:
Henri Gomez wrote:
AJP 1.5 should support automatic discovery of tomcat backend, new
systems and new webapps.
That's the current need for many of us when adding tomcats / webapp
behind Apache 2 webservers. In such case we need to restart them and
it's sad.
How could it be
Here my wishes list:
a) Clearer/better Loadbalancing Algo
- better understanding of domain/partition based strategy ( I have
detect some problemes here)
- busy strategy -
http://issues.apache.org/bugzilla/show_bug.cgi?id=36138
- real load strategy ( ask tomcats before balance the
Henri Gomez wrote:
AJP 1.5 should support automatic discovery of tomcat backend, new
systems and new webapps.
That's the current need for many of us when adding tomcats / webapp
behind Apache 2 webservers. In such case we need to restart them and
it's sad.
How could it be accomplished, may be
Yes, this is a valid case, but as I said, I think it could be added
without breaking binary compatibility. But if we just can't find one -
I think it would be far better to use a real protocol, with some
build-in extensibility - rather than invent our own brand-new protocol
or ( even worse ) patch
On 10/25/05, Mladen Turk [EMAIL PROTECTED] wrote:
Costin Manolache wrote:
DBUS is a good example in IMO - I'm not
saying to use their impl, which doesn't fit, just the protocol spec.
The major power of AJP protocol is known-header-name indexing, and
IMHO there is no other protocol that is
- Original Message -
From: William A. Rowe, Jr. [EMAIL PROTECTED]
To: dev@tomcat.apache.org
Sent: Monday, October 24, 2005 1:52 PM
Subject: Status/Authority of AJP/1.5
Questions since some interesting ideas have popped up with respect to the
next flavor of AJP... firstoff, who holds
I tought some time ago AJP was 'deprecated' - to be replaced with
plain HTTP and mod_proxy ?
Costin
On 10/24/05, Bill Barker [EMAIL PROTECTED] wrote:
- Original Message -
From: William A. Rowe, Jr. [EMAIL PROTECTED]
To: dev@tomcat.apache.org
Sent: Monday, October 24, 2005 1:52 PM
- Original Message -
From: Costin Manolache [EMAIL PROTECTED]
To: Tomcat Developers List dev@tomcat.apache.org
Sent: Monday, October 24, 2005 3:11 PM
Subject: Re: Status/Authority of AJP/1.5
I tought some time ago AJP was 'deprecated' - to be replaced with
plain HTTP and mod_proxy
I see. Sorry, I've been sleeping for quite a while, I'm slowly getting
up to speed with the latest developments.
Are you saying that mod_proxy_ajp is significantly faster than
mod_proxy ? That's interesting.
To answer your question - ajp10 and ajp11 were used in JServ,
developed in Apache.
Ajp12
10 matches
Mail list logo