Return-Path:
Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org
Received: (qmail 90928 invoked from network); 25 Nov 2003 18:55:40 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
by minotaur-2.apache.org with SMTP; 25 Nov 2003 18:55:40 -0000
Received: (qmail 31689 invoked by uid 500); 25 Nov 2003 18:38:42 -0000
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 31638 invoked by uid 500); 25 Nov 2003 18:38:42 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe:
List-Subscribe:
List-Help:
List-Post:
List-Id: "Tomcat Developers List"
Reply-To: "Tomcat Developers List"
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 31624 invoked by uid 500); 25 Nov 2003 18:38:42 -0000
Received: (qmail 31620 invoked from network); 25 Nov 2003 18:38:41 -0000
Received: from unknown (HELO minotaur.apache.org) (209.237.227.194)
by daedalus.apache.org with SMTP; 25 Nov 2003 18:38:41 -0000
Received: (qmail 81880 invoked by uid 1670); 25 Nov 2003 18:38:49 -0000
Date: 25 Nov 2003 18:38:49 -0000
Message-ID: <20031125183849.81879.qmail@minotaur.apache.org>
From: yoavs@apache.org
To: jakarta-tomcat-catalina-cvs@apache.org
Subject: cvs commit: jakarta-tomcat-catalina/webapps/docs balancer-howto.xml
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N
yoavs 2003/11/25 10:38:49
Modified: webapps/docs balancer-howto.xml
Log:
Updated
Revision Changes Path
1.2 +17 -5 jakarta-tomcat-catalina/webapps/docs/balancer-howto.xml
Index: balancer-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/balancer-howto.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- balancer-howto.xml 25 Nov 2003 18:22:30 -0000 1.1
+++ balancer-howto.xml 25 Nov 2003 18:38:49 -0000 1.2
@@ -23,7 +23,13 @@
environments. Rather, it is a simple, pure Java, easily extensible, and fast
way to direct traffic among multiple servers.
-
+
+Although balancer ships with tomcat, it is not tomcat-specific and runs
+on other containers without any modification. The balancer webapp
+requires a Servlet Specification 2.3 or later container if you wish
+to use a filter to redirect traffic. If you wish to redirect traffic
+using a servlet, you may use any servlet container.
+
@@ -64,7 +70,7 @@
should be JavaBeans (public no-args constructor, public
setter method setXXX for property xxx), as they are
instantiated by Jakarta Commons Digester. Feel free
-to inquire on the tomcat-user mailist list regarding
+to inquire on the tomcat-user mailing list regarding
the availability of rules of the inclusion of your rules
in the distribution.
@@ -72,8 +78,8 @@
Rules are assembled into RuleChains. Each BalancerFilter
(or Servlet/JSP) refers to one RuleChain when making its
-redirection decisions. Not that you are not restricted
-to having one filter mapped to /*, as is the default
+redirection decisions. Note that you are not restricted
+to having one filter mapped to /* as done in the sample
configuration. You can configure as many filters as
desired, using the full filter mapping possibilities defined
in the Servlet Specification. Each filter will have
@@ -83,7 +89,6 @@
-Here is the flow of events in the balancer:
- You write a rules configuration file containing various
rules and redirection locations.
@@ -99,6 +104,13 @@
+
+
+
+
+Please direct questions, comments, suggestions, etc. to the
+tomcat-user mailing list. Thank you.
+