From b563ebbaeae63136beae4e7eae3b30e021a0d7aa Mon Sep 17 00:00:00 2001
From: Jim Jagielski
Date: Fri, 21 Oct 2016 18:49:39 +0000
Subject: [PATCH] Fine tune description
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1766103 13f79535-47bb-0310-9956-ffa450edef68
---
docs/manual/caching.xml | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/docs/manual/caching.xml b/docs/manual/caching.xml
index a6c60276d5..7be4fa40fc 100644
--- a/docs/manual/caching.xml
+++ b/docs/manual/caching.xml
@@ -569,11 +569,13 @@ CacheDirLength 1
Caching to memcached
- The mod_cache_socache and mod_socache_memcache
- modules are used to specify that the backend storage mechanism to be used
- to store and return cached data in the memcached
server.
+ Using the mod_cache_socache module, mod_cache
+ can cache data from a variety of implementations (aka: "providers"). Using the
+ mod_socache_memcache module, for example, one can specify that
+ memcached is to be used as the
+ the backend storage mechanism.
- Typically the module will be configured as so;
+ Typically the module will be configured as so:
CacheEnable socache /
@@ -582,7 +584,12 @@ CacheSocache memcache:memcd.example.com:11211
Additional memcached
servers can be specified by
appending them to the end of the CacheSocache memcache:
- line seperated by commas.
+ line separated by commas:
+
+
+CacheEnable socache /
+CacheSocache memcache:mem1.example.com:11211,mem2.example.com:11212
+
This format is also used with the other various mod_cache_socache
providers. For example:
--
2.40.0