Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: error (idunn.apache.osuosl.org: domain apache.org from
 212.27.42.28 cause and error)
Message-ID: <451A419E.3040504@apache.org>
Date: Wed, 27 Sep 2006 11:17:18 +0200
From: Remy Maucherat <remm@apache.org>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: [6.0] Updates
References: <45193284.1080407@apache.org>
 <EE888F7A-949F-4666-AC2F-1C94E8D133AA@objektpark.de>
 <45195205.70201@hanik.com>
 <A2D68007-BF08-4E37-8E93-1D043036BFD3@objektpark.de>
In-Reply-To: <A2D68007-BF08-4E37-8E93-1D043036BFD3@objektpark.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Peter Rossbach wrote:
> Hi Filip,
> 
> I thing many people use the current cluster implementation. For those 
> people I want spend my time to sync two branches :-)
> Some people ask me to start experiments with new Servlet and JSP API's 
> or the new connector implementation but with
> the old cluster API. Let the user the choice,like APR or Java HTTP 
> Connector.

This does not make much sense here, as the new implementation does the 
exact same thing as the other one (unlike the connectors). Did you test 
the new clustering ? How does it compare to the old one ?

There's no need for two clustering implementations, so one of them needs 
to be chosen. The other one may be developed in the sandbox and provided 
as an alternative (in a separate download), but I think that's time 
which would be wasted. BTW, a major release is also the best opportunity 
to make some changes in configuration. If it's not done now, then we 
would have to keep both for a long time.

R�my


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