Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-Id: <200404010838.i318cLgP008398@kyle.globalnet.hr>
Reply-To: <mturk@apache.org>
From: "Mladen Turk" <mturk@apache.org>
To: "'Tomcat Developers List'" <tomcat-dev@jakarta.apache.org>
Subject: RE: TC evolment
Date: Thu, 1 Apr 2004 10:18:09 +0200
Organization: Apache Software Foundation
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcQXvfnGXHHl0t00S1a3yHPYxuxjAgAAZUPw
In-Reply-To: <406BC9A7.20203@apache.org>

 
> -----Original Message-----
> From: Henri Gomez
> >> I think that we need to change the thinking perspective 
> from TC being 
> >> a 'helper' to TC being a 'workhorse'.
> > Interesting idea Mladen.
> Next idea.
> 
> If we drop Apache 2.0 support we need to have jk/jk2 jobs 
> done somewhere  :
> What about Tomcat 5 & Coyote as a ajp13 dispatcher with 
> advances and fine tuning rules, which could be updated in 
> real time in via JMX ?
>

Yes something like that, It will allow mod_jk2 lb features and header
preproc, but in pure Java, and it'll need to expose some kind of the API,
usable from native code.
Having that in Java will allow dynamic config either using JMX or some other
technology.
Will it use ajp13 as a messaging protocol? I don't know yet.

MT.


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