summaryrefslogtreecommitdiff
path: root/docs/topics/cache.txt
diff options
context:
space:
mode:
authorNick Pope <nick.pope@flightdataservices.com>2020-08-15 21:34:32 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2020-09-02 08:51:17 +0200
commita6291394256aa758d74eec9ce0cfae8aea6475f2 (patch)
tree4fab7beaca627ae1448400ad3fe72b6fe08d7e7e /docs/topics/cache.txt
parent0bf627f0b2f868cdcc53ac12cc7f390901d4b83d (diff)
Refs #29887, Refs #24212 -- Added servers configuration hook for memcached backends.
The servers property can be overridden to allow memcached backends to alter the server configuration prior to it being passed to instantiate the client. This allows avoidance of documentation for per-backend differences, e.g. stripping the 'unix:' prefix for pylibmc.
Diffstat (limited to 'docs/topics/cache.txt')
-rw-r--r--docs/topics/cache.txt9
1 files changed, 0 insertions, 9 deletions
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index cc9b22ae65..ccaa82277f 100644
--- a/docs/topics/cache.txt
+++ b/docs/topics/cache.txt
@@ -114,15 +114,6 @@ In this example, Memcached is available through a local Unix socket file
}
}
-When using the ``pylibmc`` binding, do not include the ``unix:/`` prefix::
-
- CACHES = {
- 'default': {
- 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
- 'LOCATION': '/tmp/memcached.sock',
- }
- }
-
One excellent feature of Memcached is its ability to share a cache over
multiple servers. This means you can run Memcached daemons on multiple
machines, and the program will treat the group of machines as a *single*