httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pct...@apache.org
Subject svn commit: r569203 - in /httpd/httpd/branches/2.2.x/docs/manual: caching.html.en caching.xml
Date Fri, 24 Aug 2007 00:48:10 GMT
Author: pctony
Date: Thu Aug 23 17:48:09 2007
New Revision: 569203

URL: http://svn.apache.org/viewvc?rev=569203&view=rev
Log:
Updated as per Igor Galić (a.k.a. #Apache jmcg)  docs@ email.

nobomb set in Cream/WinVim

(Backported to 2.2)

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/caching.html.en
    httpd/httpd/branches/2.2.x/docs/manual/caching.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/caching.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/caching.html.en?rev=569203&r1=569202&r2=569203&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/caching.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/caching.html.en Thu Aug 23 17:48:09 2007
@@ -564,14 +564,14 @@
       
 
       <p>To store items in the cache, <code class="module"><a href="./mod/mod_disk_cache.html">mod_disk_cache</a></code>
creates
-      a 22 character hash of the url being requested. Thie hash incorporates
+      a 22 character hash of the URL being requested. This hash incorporates
       the hostname, protocol, port, path and any CGI arguments to the URL,
       to ensure that multiple URLs do not collide.</p>
 
       <p>Each character may be any one of 64-different characters, which mean
       that overall there are 22^64 possible hashes. For example, a URL might
       be hashed to <code>xyTGxSMO2b68mBCykqkp1w</code>. This hash is used
-      as a prefix for the naming of the files specific to that url within
+      as a prefix for the naming of the files specific to that URL within
       the cache, however first it is split up into directories as per
       the <code class="directive"><a href="./mod/mod_disk_cache.html#cachedirlevels">CacheDirLevels</a></code>
and
       <code class="directive"><a href="./mod/mod_disk_cache.html#cachedirlength">CacheDirLength</a></code>

@@ -602,15 +602,15 @@
       With the setting of "2" used in the above example, a grand
       total of 4096 subdirectories can ultimately be created. With
       1 million files cached, this works out at roughly 245 cached 
-      urls per directory.</p>
+      URLs per directory.</p>
 
-      <p>Each url uses at least two files in the cache-store. Typically
+      <p>Each URL uses at least two files in the cache-store. Typically
       there is a ".header" file, which includes meta-information about 
-      the url, such as when it is due to expire and a ".data" file
+      the URL, such as when it is due to expire and a ".data" file
       which is a verbatim copy of the content to be served.</p>
 
       <p>In the case of a content negotiated via the "Vary" header, a
-      ".vary" directory will be created for the url in question. This 
+      ".vary" directory will be created for the URL in question. This 
       directory will have multiple ".data" files corresponding to the
       differently negotiated content.</p>
     

Modified: httpd/httpd/branches/2.2.x/docs/manual/caching.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/caching.xml?rev=569203&r1=569202&r2=569203&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/caching.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/caching.xml Thu Aug 23 17:48:09 2007
@@ -624,14 +624,14 @@
       <title>Understanding the Cache-Store</title>
 
       <p>To store items in the cache, <module>mod_disk_cache</module> creates
-      a 22 character hash of the url being requested. Thie hash incorporates
+      a 22 character hash of the URL being requested. This hash incorporates
       the hostname, protocol, port, path and any CGI arguments to the URL,
       to ensure that multiple URLs do not collide.</p>
 
       <p>Each character may be any one of 64-different characters, which mean
       that overall there are 22^64 possible hashes. For example, a URL might
       be hashed to <code>xyTGxSMO2b68mBCykqkp1w</code>. This hash is used
-      as a prefix for the naming of the files specific to that url within
+      as a prefix for the naming of the files specific to that URL within
       the cache, however first it is split up into directories as per
       the <directive module="mod_disk_cache">CacheDirLevels</directive> and
       <directive module="mod_disk_cache">CacheDirLength</directive> 
@@ -662,15 +662,15 @@
       With the setting of "2" used in the above example, a grand
       total of 4096 subdirectories can ultimately be created. With
       1 million files cached, this works out at roughly 245 cached 
-      urls per directory.</p>
+      URLs per directory.</p>
 
-      <p>Each url uses at least two files in the cache-store. Typically
+      <p>Each URL uses at least two files in the cache-store. Typically
       there is a ".header" file, which includes meta-information about 
-      the url, such as when it is due to expire and a ".data" file
+      the URL, such as when it is due to expire and a ".data" file
       which is a verbatim copy of the content to be served.</p>
 
       <p>In the case of a content negotiated via the "Vary" header, a
-      ".vary" directory will be created for the url in question. This 
+      ".vary" directory will be created for the URL in question. This 
       directory will have multiple ".data" files corresponding to the
       differently negotiated content.</p>
     </section>



Mime
View raw message