Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <435DDDBB.9070004@apache.org>
Date: Tue, 25 Oct 2005 09:24:43 +0200
From: Mladen Turk <mturk@apache.org>
User-Agent: Mozilla
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: Status/Authority of AJP/1.5
References: <435D4970.9070601@rowe-clan.net>
	 <00e201c5d8e3$959c6e40$7037a8c0@nt.wilshire.com>
	 <96e4b5230510241511p58422cc5n3d32a8550f741271@mail.gmail.com>
	 <435D822E.3060301@rowe-clan.net>
	 <96e4b5230510241831i5c8d252ek4b5d0f92827da0a2@mail.gmail.com>
 <6291fc850510242321h3fca5e1am@mail.gmail.com>
In-Reply-To: <6291fc850510242321h3fca5e1am@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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 via a master tomcat who will give
> the tomcat farm topology to Apache HTTP2.
> 
> What do you think ?
>

Although I was evangelizing the new protocol for a long time...
Looking more deeply on the subject IMHO there is no much purpose for
developing such stuff unless the HTTPD offers the dynamic
reconfiguration, and I doubt something like that will be considered
before Apache 3.0 (as I understood).

Introducing new protocol would bring more problems if we try to
implement it within current web servers then it would resolve, so
it might have sense only if Apache would implement dynamic config
in the future.

We should use our (quite limited right now) resources for cleaning
up the existing JK codebase and try to extend the existing protocol
without braking backward compatibility.

One of the advances would be to extend the CPING/CPONG messages
with worker/balancer status data, so that we can collect data in
the runtime like load, etc... The other would be to introduce private
headers within AJP channels for status data exchange between nodes.

Those two things would resolve much of the existing problems caused
by 'dummy' one way communication, and beside cleanup of the exiting
code, it is the reason for creating a 1.3 branch.

Regards,
Mladen.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org