mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Added 'key_prefix' keyword argument to cache_page()
This was available before r11586, but undocumented. It has now been re-added with documentation and explicit support, as it seems like a useful feature and people were using it before. git-svn-id: http://code.djangoproject.com/svn/django/trunk@11595 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
a97648a7e0
commit
6e3a72585a
3 changed files with 25 additions and 4 deletions
|
@ -361,6 +361,17 @@ then requests to ``/foo/1/`` and ``/foo/23/`` will be cached separately, as
|
|||
you may expect. But once a particular URL (e.g., ``/foo/23/``) has been
|
||||
requested, subsequent requests to that URL will use the cache.
|
||||
|
||||
``cache_page`` can also take an optional keyword argument, ``key_prefix``, which
|
||||
works in the same way as the ``CACHE_MIDDLEWARE_KEY_PREFIX`` setting for the
|
||||
middleware. It can be used like this::
|
||||
|
||||
my_view = cache_page(my_view, 60 * 15, key_prefix="site1")
|
||||
|
||||
Or, using Python 2.4's decorator syntax::
|
||||
|
||||
@cache_page(60 * 15, key_prefix="site1")
|
||||
def my_view(request):
|
||||
|
||||
Specifying per-view cache in the URLconf
|
||||
----------------------------------------
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue