On Feb 9, 2008, at 6:15 PM, Ruediger Pluem wrote:
On 02/09/2008 04:28 PM, Dirk-Willem van Gulik wrote:
Ok - so I think this compromise makes the most sense
ALL everything except demo, experimental and things like
bucketeer, import/export filters.
MOST all the stable things - including the proxy modules (And
given the questions on mailing lists and wiki's - that really
is something people seem to exepct).
And at the same exempt ssl because of crypto and mod_mem_cache
as it has not had that much tender lover and care recently.
Makes sense ?
Dw.
Index: modules/cache/config.m4
===================================================================
--- modules/cache/config.m4 (revision 620132)
+++ modules/cache/config.m4 (working copy)
@@ -4,7 +4,7 @@
APACHE_MODPATH_INIT(cache)
-APACHE_MODULE(file_cache, File cache, , , no)
+APACHE_MODULE(file_cache, File cache)
dnl # list of object files for mod_cache
cache_objs="dnl
@@ -19,8 +19,8 @@
cache_pqueue.lo dnl
cache_hash.lo dnl
"
-APACHE_MODULE(cache, dynamic file caching, $cache_objs, , no)
-APACHE_MODULE(disk_cache, disk caching module, , , no)
+APACHE_MODULE(cache, dynamic file caching, $cache_objs, , yes)
+APACHE_MODULE(disk_cache, disk caching module, , , most)
Hm. Does this make sense? We now have the cache enabled by default,
but
no backend provider. Thus mod_cache cannot be used in this case.
Unless you swap in some third party (memcached, distcache, commercial
netapp) module.
Only most / all / --enable-disk-cache give us mod_cache with at least
one backend provider.
Dw.
