Changeset 8980
- Timestamp:
- 09/07/08 17:55:31 (2 months ago)
- Files:
-
- django/trunk/docs/topics/cache.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/topics/cache.txt
r8843 r8980 187 187 188 188 While Django includes support for a number of cache backends out-of-the-box, 189 sometimes you will want to use a customised version or your own backend. To 190 use an external cache backend with Django, use a Python import path as the 191 scheme portion (the part before the initial colon) of the ``CACHE_BACKEND`` 192 URI, like so:: 189 sometimes you might want to use a customized cache backend. To use an external 190 cache backend with Django, use a Python import path as the scheme portion (the 191 part before the initial colon) of the ``CACHE_BACKEND`` URI, like so:: 193 192 194 193 CACHE_BACKEND = 'path.to.backend://' … … 198 197 ``django/core/cache/backends/`` directory of the Django source. 199 198 200 Note: Without a really compelling reason, like a host that doesn't support the 201 them, you should stick to the cache backends included with Django. They've 202 been really well-tested and are quite easy to use. 203 199 Note: Without a really compelling reason, such as a host that doesn't support 200 the them, you should stick to the cache backends included with Django. They've 201 been well-tested and are easy to use. 204 202 205 203 CACHE_BACKEND arguments
