trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1132916 - in /trafficserver/site/branches/ats-cms/content/docs/trunk: STATUS admin/hierachical-caching/index.en.mdtext
Date Tue, 07 Jun 2011 08:55:07 GMT
Author: igalic
Date: Tue Jun  7 08:55:06 2011
New Revision: 1132916

URL: http://svn.apache.org/viewvc?rev=1132916&view=rev
Log:
Remove the ICP Peering paragraph from the hierachical caching document
<!-- it's commented out, so it can be easily re-added, once the code is actually supported
again -->

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS?rev=1132916&r1=1132915&r2=1132916&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS Tue Jun  7 08:55:06 2011
@@ -60,7 +60,7 @@ getting-started - done
 http-proxy-caching - done
 reverse-proxy-http-redirects - done
 explicit-proxy-caching - done
-hierachical-caching
+hierachical-caching - done (commented out ICP peering, because it's not really supported
right now)
 configuring-cache
 monitoring-traffic
 configuring-traffic-server

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext?rev=1132916&r1=1132915&r2=1132916&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext
Tue Jun  7 08:55:06 2011
@@ -23,13 +23,9 @@ Traffic Server can participate in cache 
 in one cache are routed to other regional caches, thereby leveraging the contents 
 and proximity of nearby caches. 
 
-This chapter discusses the following topics: 
+[TOC]()
 
-* [Understanding Cache Hierarchies](#UnderstandingCacheHierarchies)
-* [Parent Caching](#ParentCaching)
-* [ICP Peering](#ICPPeering)
-
-## Understanding Cache Hierarchies ## {#UnderstandingCacheHierarchies}
+# Understanding Cache Hierarchies # {#UnderstandingCacheHierarchies}
 
 A cache hierarchy consists of cache levels that communicate with each other. 
 Traffic Server supports several types of cache hierarchies. All cache hierarchies 
@@ -40,9 +36,9 @@ child cache is a cache for which Traffic
 Traffic Server supports the following hierarchical caching options: 
 
 * [Parent Caching](#ParentCaching)
-* [ICP (Internet Cache Protocol) Peering](#ICPPeering)
+<!-- * [ICP (Internet Cache Protocol) Peering](#ICPPeering) -->
 
-## Parent Caching ## {#ParentCaching}
+# Parent Caching # {#ParentCaching}
 
 If a Traffic Server node cannot find a requested object in its cache, then 
 it searches a parent cache (which itself can search other caches) before finally 
@@ -75,7 +71,7 @@ parent’s configuration). The parent
 to Traffic Server (its child), where it is cached and served to the client. 
  
 
-### Parent Failover ### {#ParentFailover}
+## Parent Failover ## {#ParentFailover}
 
 Traffic Server supports use of several parent caches. This ensures that if 
 one parent cache is not available, another parent cache can service client 
@@ -85,11 +81,11 @@ When you configure your Traffic Server t
 Server detects when a parent is not available and sends missed requests to 
 another parent cache. If you specify more than two parent caches, then the 
 order in which the parent caches are queried depends upon the parent proxy 
-rules configured in the [parent.config](files.htm#parent.config) configuration 
+rules configured in the [parent.config](../configuration-files/parent.config) configuration

 file. By default, the parent caches are queried in the order they are listed 
 in the configuration file. 
 
-### Configuring Traffic Server to Use a Parent Cache  ### {#ConfiguringTSUseaParentCache}
+## Configuring Traffic Server to Use a Parent Cache  ## {#ConfiguringTSUseaParentCache}
 
 To configure Traffic Server to use one or more parent caches, you must complete 
 the following steps: 
@@ -103,9 +99,8 @@ the following steps: 
 is needed for the Traffic Server parent cache. 
 
 
-##### Configure Traffic Server to use a parent cache:  ##### {#ConfigureTSuseaparentcache}
-
-Edit the following variable [_`proxy.config.http.parent_proxy_routing_enable`_](../configuration-files/records.config#proxy.config.http.parent_proxy_routing_enable)
in `records.config` file.
+Configure Traffic Server to use a parent cache by editing the following variable
+[_`proxy.config.http.parent_proxy_routing_enable`_](../configuration-files/records.config#proxy.config.http.parent_proxy_routing_enable)
in `records.config` file.
 
 Edit the [`parent.config`](../configuration-files/parent.config) file located in the Traffic
Server `config` directory to set
 parent proxy rules to specify the parent cache to which you want missed requests to be forwarded;
@@ -113,6 +108,7 @@ parent proxy rules to specify the parent
 The following example configures Traffic Server to route all requests containing the regular
expression `politics`
 and the path `/viewpoint` directly to the origin server (bypassing any parent hierarchies):
 
+    :::text
     url_regex=politics prefix=/viewpoint go_direct=true
 
 The following example configures Traffic Server to direct all missed requests with URLs beginning
@@ -120,12 +116,15 @@ with `http://host1` to the parent cache 
 requests are forwarded to `parent2`. Because `round-robin=true`, Traffic Server goes through
the
 parent cache list in a round-robin based on client IP address.
 
+    :::text
     dest_host=host1 scheme=http parent="parent1;parent2" round-robin=strict
 
 
 Run the command `traffic_line -x` to apply the configuration changes.
 
-## ICP Peering ## {#ICPPeering}
+<!-- As of yet, this is not supported.
+
+# ICP Peering # {#ICPPeering}
 
 The Internet Cache Protocol (ICP) is used by proxy caches to exchange information 
 about their content. ICP query messages ask other caches if they are storing 
@@ -158,9 +157,7 @@ must perform the following tasks: 
 * Set the ICP query timeout. 
 * Identify the ICP peers (siblings and parents) with which Traffic Server can communicate.
 
-##### To configure Traffic Server to use an ICP cache hierarchy:  ##### {#configureTSuseanICPcachehierarchy}
-
-Edit the following variables in [`records.config`](../configuration-files/records.config)
file:
+To configure Traffic Server to use an ICP cache hierarchy edit the following variables in
[`records.config`](../configuration-files/records.config) file:
 
 * [_`proxy.config.icp.enabled`_](../configuration-files/records.config#proxy.config.icp.enabled)
 * [_`proxy.config.icp.icp_port`_](../configuration-files/records.config#proxy.config.icp.port)
@@ -172,3 +169,4 @@ For each ICP peer you want to identify, 
 
 Run the command `traffic_line -x` to apply the configuration changes.
 
+-->



Mime
View raw message