httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stodd...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_cache.xml mod_mem_cache.xml
Date Wed, 18 Dec 2002 22:12:37 GMT
stoddard    2002/12/18 14:12:37

  Modified:    docs/manual/mod mod_cache.xml mod_mem_cache.xml
  Log:
  Rename CacheMaxStreamingBuffer to MCacheMaxStreamingBuffer and move it
  out of mod_cache and into mod_mem_cache. Note default buffer size of
  the lesser of 100000 or MCacheMaxObjectSize
  
  Revision  Changes    Path
  1.13      +1 -42     httpd-2.0/docs/manual/mod/mod_cache.xml
  
  Index: mod_cache.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_cache.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- mod_cache.xml	6 Nov 2002 17:53:30 -0000	1.12
  +++ mod_cache.xml	18 Dec 2002 22:12:37 -0000	1.13
  @@ -63,6 +63,7 @@
           <directive module="mod_mem_cache">MCacheMinObjectSize</directive>
           <directive module="mod_mem_cache">MCacheMaxObjectSize</directive>
           <directive module="mod_mem_cache">MCacheRemovalAlgorithm</directive>
  +        <directive module="mod_mem_cache">MCacheMaxStreamingBuffer</directive>
         </directivelist>
       </related>
   </section>
  @@ -310,48 +311,6 @@
       <note type="warning"><title>Note:</title>
         This feature is currently <em>not</em> implemented.
       </note>
  -</usage>
  -</directivesynopsis>
  -
  -<directivesynopsis>
  -<name>CacheMaxStreamingBuffer</name>
  -<description>Maximum amount of a streamed response to buffer in memory
  -before declaring the response uncacheable</description>
  -<syntax>CacheMaxStreamingBuffer <var>size_in_bytes</var></syntax>
  -<default>CacheMaxStreamingBuffer 0</default>
  -<contextlist><context>server config</context><context>virtual host</context>
  -</contextlist>
  -
  -<usage>
  -    <p>The <directive>CacheMaxStreamingBuffer</directive> directive
  -    specifies the maximum number of bytes of a streamed response to
  -    buffer before deciding that the response is too big to cache.
  -    A streamed response is one in which the entire content is not
  -    immediately available and in which the <code>Content-Length</code>
  -    may not be known. Sources of streaming responses include proxied
  -    responses and the output of CGI scripts. By default, a streamed
  -    response will <em>not</em> be cached unless it has a
  -    <code>Content-Length</code> header. The reason for this is to
  -    avoid using a large amount of memory to buffer a partial response
  -    that might end up being too large to fit in the cache.
  -    The <directive>CacheMaxStreamingBuffer</directive> directive allows
  -    buffering of streamed responses that don't contain a
  -    <code>Content-Length</code> up to the specified maximum amount of
  -    space. If the maximum buffer space is reached, the buffered
  -    content is discarded and the attempt to cache is abandoned.</p>
  -
  -    <note><title>Note:</title>
  -      <p>Using a nonzero value for <directive
  -      >CacheMaxStreamingBuffer</directive> will not delay the transmission
  -      of the response to the client.  As soon as <module>mod_cache</module>
  -      copies a block of streamed content into a buffer, it sends the block
  -      on to the next output filter for delivery to the client.</p>
  -    </note>
  -
  -    <example>
  -      # Enable caching of streamed responses up to 64KB:<br />
  -      CacheMaxStreamingBuffer 65536
  -    </example>
   </usage>
   </directivesynopsis>
   
  
  
  
  1.5       +42 -0     httpd-2.0/docs/manual/mod/mod_mem_cache.xml
  
  Index: mod_mem_cache.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_mem_cache.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- mod_mem_cache.xml	9 Dec 2002 23:52:44 -0000	1.4
  +++ mod_mem_cache.xml	18 Dec 2002 22:12:37 -0000	1.5
  @@ -158,4 +158,46 @@
   </usage>
   </directivesynopsis>
   
  +<directivesynopsis>
  +<name>MCacheMaxStreamingBuffer</name>
  +<description>Maximum amount of a streamed response to buffer in memory
  +before declaring the response uncacheable</description>
  +<syntax>MCacheMaxStreamingBuffer <var>size_in_bytes</var></syntax>
  +<default>MCacheMaxStreamingBuffer the smaller of 100000 or MCacheMaxObjectSize</default>
  +<contextlist><context>server config</context>
  +</contextlist>
  +
  +<usage>
  +    <p>The <directive>MCacheMaxStreamingBuffer</directive> directive
  +    specifies the maximum number of bytes of a streamed response to
  +    buffer before deciding that the response is too big to cache.
  +    A streamed response is one in which the entire content is not
  +    immediately available and in which the <code>Content-Length</code>
  +    may not be known. Sources of streaming responses include proxied
  +    responses and the output of CGI scripts. By default, a streamed
  +    response will <em>not</em> be cached unless it has a
  +    <code>Content-Length</code> header. The reason for this is to
  +    avoid using a large amount of memory to buffer a partial response
  +    that might end up being too large to fit in the cache.
  +    The <directive>MCacheMaxStreamingBuffer</directive> directive allows
  +    buffering of streamed responses that don't contain a
  +    <code>Content-Length</code> up to the specified maximum amount of
  +    space. If the maximum buffer space is reached, the buffered
  +    content is discarded and the attempt to cache is abandoned.</p>
  +
  +    <note><title>Note:</title>
  +      <p>Using a nonzero value for <directive>MCacheMaxStreamingBuffer</directive>

  +      will not delay the transmission of the response to the client.
  +      As soon as <module>mod_mem_cache</module> copies a block of streamed
  +      content into a buffer, it sends the block on to the next output
  +      filter for delivery to the client.</p>
  +    </note>
  +
  +    <example>
  +      # Enable caching of streamed responses up to 64KB:<br />
  +      MCacheMaxStreamingBuffer 65536
  +    </example>
  +</usage>
  +</directivesynopsis>
  +
   </modulesynopsis>
  
  
  

Mime
View raw message