Return-Path: 
 <cvs-return-27007-apmail-httpd-cvs-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-cvs-archive@www.apache.org
Received: (qmail 14411 invoked from network); 1 Aug 2007 17:53:00 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 1 Aug 2007 17:53:00 -0000
Received: (qmail 27660 invoked by uid 500); 1 Aug 2007 17:52:59 -0000
Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org
Received: (qmail 27617 invoked by uid 500); 1 Aug 2007 17:52:59 -0000
Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:cvs-help@httpd.apache.org>
list-unsubscribe: <mailto:cvs-unsubscribe@httpd.apache.org>
List-Post: <mailto:cvs@httpd.apache.org>
List-Id: <cvs.httpd.apache.org>
Delivered-To: mailing list cvs@httpd.apache.org
Received: (qmail 27596 invoked by uid 99); 1 Aug 2007 17:52:59 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2007 10:52:59 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2007 17:52:26 +0000
Received: by eris.apache.org (Postfix, from userid 65534)
	id 44E751A981A; Wed,  1 Aug 2007 10:52:27 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r561887 - in /httpd/httpd/trunk/docs/manual:
 misc/rewriteguide.html.en misc/rewriteguide.xml
 rewrite/rewrite_guide_advanced.html.en rewrite/rewrite_guide_advanced.xml
Date: Wed, 01 Aug 2007 17:52:25 -0000
To: cvs@httpd.apache.org
From: slive@apache.org
X-Mailer: svnmailer-1.1.0
Message-Id: <20070801175227.44E751A981A@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: slive
Date: Wed Aug  1 10:52:15 2007
New Revision: 561887

URL: http://svn.apache.org/viewvc?view=rev&rev=561887
Log:
Fix DNS load balancing example.

Submitted by: Takashi Sato <serai lans-tv.com>
PR: 23501

Modified:
    httpd/httpd/trunk/docs/manual/misc/rewriteguide.html.en
    httpd/httpd/trunk/docs/manual/misc/rewriteguide.xml
    httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en
    httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.xml

Modified: httpd/httpd/trunk/docs/manual/misc/rewriteguide.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/misc/rewriteguide.html.en?view=diff&rev=561887&r1=561886&r2=561887
==============================================================================
--- httpd/httpd/trunk/docs/manual/misc/rewriteguide.html.en (original)
+++ httpd/httpd/trunk/docs/manual/misc/rewriteguide.html.en Wed Aug  1 10:52:15 2007
@@ -1262,19 +1262,15 @@
               <p>Then you additionally add the following entry:</p>
 
 <div class="example"><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
 </pre></div>
 
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load

Modified: httpd/httpd/trunk/docs/manual/misc/rewriteguide.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/misc/rewriteguide.xml?view=diff&rev=561887&r1=561886&r2=561887
==============================================================================
--- httpd/httpd/trunk/docs/manual/misc/rewriteguide.xml (original)
+++ httpd/httpd/trunk/docs/manual/misc/rewriteguide.xml Wed Aug  1 10:52:15 2007
@@ -1263,19 +1263,15 @@
               <p>Then you additionally add the following entry:</p>
 
 <example><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
 </pre></example>
 
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load

Modified: httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en?view=diff&rev=561887&r1=561886&r2=561887
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en Wed Aug  1 10:52:15 2007
@@ -619,19 +619,15 @@
               <p>Then you additionally add the following entry:</p>
 
 <div class="example"><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
 </pre></div>
 
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load

Modified: httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.xml?view=diff&rev=561887&r1=561886&r2=561887
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.xml (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.xml Wed Aug  1 10:52:15 2007
@@ -623,19 +623,15 @@
               <p>Then you additionally add the following entry:</p>
 
 <example><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
 </pre></example>
 
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load