Commit e38c2779 authored by Justin Erenkrantz's avatar Justin Erenkrantz
Browse files

At long last, promote mod_cache and friends out of experimental/. 

Also, take quick pass through docs files to remove experimental label for them.

Reviewed by: Paul Querna, Bill Stoddard, Justin Erenkrantz


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@106737 13f79535-47bb-0310-9956-ffa450edef68
parent 43aa8f51

CHANGES

+3 −1
Original line number Diff line number Diff line
@@ -2,6 +2,8 @@ Changes with Apache 2.1.2-dev 














  [Remove entries to the current 2.0 section below, when backported]



























  *) mod_cache/mod_mem_cache/mod_disk_cache: Move out of experimental.



























  *) Upgraded PCRE to version 5.0. [Brian Pane]





























  *) mod_cgid: Catch configuration problem where two web server instances

































STATUS



+21
−35






























Original line number
Diff line number
Diff line








@@ -37,35 +37,6 @@ RELEASE SHOWSTOPPERS:





























CURRENT VOTES:





























    * Promote mod_cache from experimental to non-experimental













      status (keep issues noted below in EXPERIMENTAL MODULES as













      items to be addressed as a supported module).













      +1: jerenkrantz, pquerna, stoddard













      +0: jim, bnicholes













      -1:













          There are a couple of problems that need to be resolved













      before this module is moved out of experimental. 













      1) We need to at least review and comment on the RFC violations













      2) Resolve issue of how to cache page fragements (or perhaps -if- we













      want to cache page fragements). Today, mod_cache/mod_mem_cache













      will cache #include 'virtual' requests (but not #include 'file' 













      requests). This was accomplished by making CACHE_IN a













      CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE













      filter.  But now responses cannot be cached that include the













      effects of having been run through CONTENT_SET filters













      (mod_deflate, mod_expires, etc).  We could rerun all the













      CONTENT_SET filters on the cached response, but this will not













      work in all cases. For example, mod_expires relies on installing













      the EXPIRATION filter during fixups. Contents served out of













      mod_cache (out of the quick_handler) bypass -all- the request













      line server hooks (Ryan really hated this. It is great for













      performance, but bad because of the complications listed above).



























      jerenkrantz: I think it's time.  We've done a *lot* of work to it, and













                   we think most of the blatant RFC violations are now gone.













                   mod_cache just belongs in cache/.  There may still be bugs,













                   but not likely to be major ones.





























    * httpd-std.conf and friends































      a) httpd-std.conf should be tailored by install (from src or










@@ -478,12 +449,20 @@ WISH LIST





























    * mod_cache: Handle ESI tags.





























EXPERIMENTAL MODULES:



























    Experimental modules should eventually be be promoted to fully supported













    status or removed from the repository entirely (ie, the













    'experiment' failed). This section tracks what needs to happen to 













    get the modules promoted to fully supported status.













    * mod_cache: Resolve issue of how to cache page fragements (or perhaps













      -if- we want to cache page fragements). Today, mod_cache/mod_mem_cache













      will cache #include 'virtual' requests (but not #include 'file'













      requests). This was accomplished by making CACHE_IN a













      CONTENT_SET-1 filter to force it to run before the SUBREQ_CORE













      filter.  But now responses cannot be cached that include the













      effects of having been run through CONTENT_SET filters













      (mod_deflate, mod_expires, etc).  We could rerun all the













      CONTENT_SET filters on the cached response, but this will not













      work in all cases. For example, mod_expires relies on installing













      the EXPIRATION filter during fixups. Contents served out of













      mod_cache (out of the quick_handler) bypass -all- the request













      line server hooks (Ryan really hated this. It is great for













      performance, but bad because of the complications listed above).































    mod_cache/mod_mem_cache/mod_disk_cache:

























@@ -508,6 +487,13 @@ EXPERIMENTAL MODULES:













      HTTP or SNMP?















      jerenkrantz says: Yawn.  Who cares.





























EXPERIMENTAL MODULES:



























    Experimental modules should eventually be be promoted to fully supported













    status or removed from the repository entirely (ie, the













    'experiment' failed). This section tracks what needs to happen to 













    get the modules promoted to fully supported status.





























PRs that have been suspended forever waiting for someone to















put them into 'the next release':

















































docs/manual/mod/mod_cache.xml



+0
−13






























Original line number
Diff line number
Diff line








@@ -23,15 +23,10 @@





























<name>mod_cache</name>















<description>Content cache keyed to URIs.</description>













<status>Experimental</status>















<sourcefile>mod_cache.c</sourcefile>















<identifier>cache_module</identifier>































<summary>













    <note type="warning">













      This module is experimental. Documentation is still under development...













    </note>





























    <p><module>mod_cache</module> implements an <a















    href="http://www.ietf.org/rfc/rfc2616.txt">RFC 2616</a> compliant HTTP















    content cache that can be used to cache either local or proxied content.










@@ -65,17 +60,10 @@













      <directivelist>















        <directive module="mod_disk_cache">CacheRoot</directive>















        <directive module="mod_disk_cache">CacheSize</directive>













        <directive module="mod_disk_cache">CacheGcInterval</directive>















        <directive module="mod_disk_cache">CacheDirLevels</directive>















        <directive module="mod_disk_cache">CacheDirLength</directive>













        <directive module="mod_disk_cache">CacheExpiryCheck</directive>















        <directive module="mod_disk_cache">CacheMinFileSize</directive>















        <directive module="mod_disk_cache">CacheMaxFileSize</directive>













        <directive module="mod_disk_cache">CacheTimeMargin</directive>













        <directive module="mod_disk_cache">CacheGcDaily</directive>













        <directive module="mod_disk_cache">CacheGcUnused</directive>













        <directive module="mod_disk_cache">CacheGcClean</directive>













        <directive module="mod_disk_cache">CacheGcMemUsage</directive>















        <directive module="mod_mem_cache">MCacheSize</directive>















        <directive module="mod_mem_cache">MCacheMaxObjectCount</directive>















        <directive module="mod_mem_cache">MCacheMinObjectSize</directive>









@@ -101,7 +89,6 @@













        &lt;IfModule mod_disk_cache.c&gt;<br />















        <indent>















          CacheRoot c:/cacheroot<br />













          CacheSize 256<br />















          CacheEnable disk  /<br />















          CacheDirLevels 5<br />















          CacheDirLength 3<br />

































docs/manual/mod/mod_disk_cache.xml



+2
−7






























Original line number
Diff line number
Diff line








@@ -23,18 +23,13 @@





























<name>mod_disk_cache</name>















<description>Content cache storage manager keyed to URIs</description>













<status>Experimental</status>















<sourcefile>mod_disk_cache.c</sourcefile>















<identifier>disk_cache_module</identifier>































<summary>













    <note type="warning">













      This module is experimental. Documentation is still under development...













    </note>





























    <p><module>mod_disk_cache</module> implements a disk based storage













    manager. It is primarily of use in conjunction with













    <module>mod_proxy</module>.</p>













    manager. It is primarily of use in conjunction













    <module>mod_cache</module>.</p>































    <p>Content is stored in and retrieved from the cache using URI based















    keys. Content with access protection is not cached.</p>

































docs/manual/mod/mod_mem_cache.xml



+0
−6






























Original line number
Diff line number
Diff line








@@ -23,16 +23,10 @@





























<name>mod_mem_cache</name>















<description>Content cache keyed to URIs</description>













<status>Experimental</status>















<sourcefile>mod_mem_cache.c</sourcefile>















<identifier>mem_cache_module</identifier>































<summary>













    <note type="warning">













      This module is experimental. Documentation is still under













      development...













    </note>





























    <p>This module <em>requires</em> the service of <module















    >mod_cache</module>. It acts as a support module for <module















    >mod_cache</module> and provides a memory based storage manager.