Skip to content

Commit

Permalink
Small wording improvements to cache.txt
Browse files Browse the repository at this point in the history
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8980 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information
adrianholovaty committed Sep 7, 2008
1 parent acf2600 commit 571f463
Showing 1 changed file with 6 additions and 8 deletions.
14 changes: 6 additions & 8 deletions docs/topics/cache.txt
Expand Up @@ -186,21 +186,19 @@ Using a custom cache backend
.. versionadded:: 1.0

While Django includes support for a number of cache backends out-of-the-box,
sometimes you will want to use a customised version or your own backend. To
use an external cache backend with Django, use a Python import path as the
scheme portion (the part before the initial colon) of the ``CACHE_BACKEND``
URI, like so::
sometimes you might want to use a customized cache backend. To use an external
cache backend with Django, use a Python import path as the scheme portion (the
part before the initial colon) of the ``CACHE_BACKEND`` URI, like so::

CACHE_BACKEND = 'path.to.backend://'

If you're building your own backend, you can use the standard cache backends
as reference implementations. You'll find the code in the
``django/core/cache/backends/`` directory of the Django source.

Note: Without a really compelling reason, like a host that doesn't support the
them, you should stick to the cache backends included with Django. They've
been really well-tested and are quite easy to use.

Note: Without a really compelling reason, such as a host that doesn't support
the them, you should stick to the cache backends included with Django. They've
been well-tested and are easy to use.

CACHE_BACKEND arguments
-----------------------
Expand Down

0 comments on commit 571f463

Please sign in to comment.