Corrected an inconsistency in the documentation regarding the way to specify the locmem and dummy cache backend. Thanks to Jens Diemer for the report.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@11750 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
47f1330be1
commit
55b6f3cf21
|
@ -179,9 +179,9 @@ Local-memory caching
|
|||
If you want the speed advantages of in-memory caching but don't have the
|
||||
capability of running Memcached, consider the local-memory cache backend. This
|
||||
cache is multi-process and thread-safe. To use it, set ``CACHE_BACKEND`` to
|
||||
``"locmem:///"``. For example::
|
||||
``"locmem://"``. For example::
|
||||
|
||||
CACHE_BACKEND = 'locmem:///'
|
||||
CACHE_BACKEND = 'locmem://'
|
||||
|
||||
Note that each process will have its own private cache instance, which means no
|
||||
cross-process caching is possible. This obviously also means the local memory
|
||||
|
@ -199,7 +199,7 @@ various places but a development/test environment where you don't want to cache
|
|||
and don't want to have to change your code to special-case the latter. To
|
||||
activate dummy caching, set ``CACHE_BACKEND`` like so::
|
||||
|
||||
CACHE_BACKEND = 'dummy:///'
|
||||
CACHE_BACKEND = 'dummy://'
|
||||
|
||||
Using a custom cache backend
|
||||
----------------------------
|
||||
|
@ -249,7 +249,7 @@ In this example, ``timeout`` is set to ``60``::
|
|||
|
||||
In this example, ``timeout`` is ``30`` and ``max_entries`` is ``400``::
|
||||
|
||||
CACHE_BACKEND = "locmem:///?timeout=30&max_entries=400"
|
||||
CACHE_BACKEND = "locmem://?timeout=30&max_entries=400"
|
||||
|
||||
Invalid arguments are silently ignored, as are invalid values of known
|
||||
arguments.
|
||||
|
|
Loading…
Reference in New Issue