Changeset 8075 for django/trunk/docs/cache.txt

Timestamp:

07/25/08 13:51:32 (4 months ago)

Author:

mtredinnick

Message:

Fixed #7398 -- Allow for custom cache-backends to be used.

Based on a patch from Lau Bech Lauritzen and Brenton Simpson.

Files:

• django/trunk/docs/cache.txt (modified) (2 diffs)

django/trunk/docs/cache.txt

@@ -7 +7 @@
-from database queries to template rendering to business logic -- to create the
-page that your site's visitor sees. This is a lot more expensive, from a
- read-a-file-off-the-filesystem
-
+
+read-a-file-off-the-filesystem 
-
-For most Web applications, this overhead isn't a big deal. Most Web
@@ -186 +186 @@
-
-    CACHE_BACKEND = 'dummy:///'
+
+Using a custom cache backend
+----------------------------
+
+**New in Django development version**
+
+While Django includes support for a number of cache backends out-of-the-box,
+sometimes you will want to use a customised verison 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::
+
+    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.
-
-CACHE_BACKEND arguments