Opened 5 years ago

Closed 5 years ago

#10066 closed (invalid)

can per-site cache and per-view cache or some low level cache work together?

Reported by: ubestim Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


can per-site cache and per-view cache or some low level cache work together?
my purpose is to cache the whole site for anonymous and cache serveral
view for registered user only.

first, i set these in per-site cache in
CACHE_BACKEND = 'memcached://'

this means only cache for anonymous.

then i set some per-view cache as below:
@cache_page(60 * 15)
def slashdot_this(request):

so view of slashdot_this will cache for register user and anonymous.

am i right?

If I have added the middleware needed for per-site cache,the cache middleware will cache again the data already cached
by my view?
Can you give more explanation in cache settings for using one of per-persite and per-view/low level and using them together?

Attachments (0)

Change History (1)

comment:1 Changed 5 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

Please ask questions like this on the django-users mailing list or in the #django IRC channel. This Trac install is only for bug reports. Thanks.

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.