svn commit: r881937 - in /websites/staging/trafficserver/trunk: cgi-bin/ content/ content/docs/trunk/admin/http-proxy-caching/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Wed Oct  9 21:17:17 2013
New Revision: 881937

Log:
Staging update by buildbot for trafficserver

Modified:
    websites/staging/trafficserver/trunk/cgi-bin/   (props changed)
    websites/staging/trafficserver/trunk/content/   (props changed)
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html

Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Oct  9 21:17:17 2013
@@ -1 +1 @@
-1530785
+1530797

Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Oct  9 21:17:17 2013
@@ -1 +1 @@
-1530785
+1530797

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html Wed Oct  9 21:17:17 2013
@@ -716,7 +716,7 @@ resources. There are several features in
 <p>All four configurations are required, for the following reasons:</p>
 <ul>
 <li><code>enable_read_while_writer</code> turns the feature on. It's off (0) by default</li>
-<li>The background fill feature should be allowed to kick in for every possible request. This is necessary, in case the writer ("first client session") goes away, someone needs to take over the session. The original client's request can go away after <code>background_fill_active_timeout</code> seconds, and the object will continue fetching in the background. The object then can start being served to another request after background_fill_completed_threshold % of the object has been fetched from origin.</li>
+<li>The background fill feature should be allowed to kick in for every possible request. This is necessary, in case the writer ("first client session") goes away, someone needs to take over the session. Hence, you should set the background fill timeouts and threshold to zero; this assures they never times out and always is allowed to kick in.</li>
 <li>The <code>proxy.config.cache.max_doc_size</code> should be unlimited (set to 0), since the object size may be unknown, and going over this limit would cause a disconnect on the objects being served.</li>
 </ul>
 <p>Once all this enabled, you have something that is very close, but not quite the same, as Squid's Collapsed Forwarding.</p>