#13283: CACHE_MIDDLEWARE_ANONYMOUS_ONLY kills anonymous caching efficiency
-----------------------------------+----------------------------------------
          Reporter:  carljm        |         Owner:  nobody                     
 
            Status:  new           |     Milestone:                             
 
         Component:  Cache system  |       Version:  SVN                        
 
        Resolution:                |      Keywords:  session accessed vary 
cookie
             Stage:  Accepted      |     Has_patch:  1                          
 
        Needs_docs:  0             |   Needs_tests:  0                          
 
Needs_better_patch:  1             |  
-----------------------------------+----------------------------------------
Comment (by carljm):

 Replying to [comment:18 natrius]:
 > This seems like a problem that should be ameliorated somehow for Django
 1.3.

 I'm planning to get back to your pull request and commit some form of it
 before Django 1.3 -- just haven't gotten there yet.

 > If we want users to be able to save memory by not caching user-specific
 pages, I have a patch to do that with a separate setting, but
 `CACHE_MIDDLEWARE_ANONYMOUS_ONLY` must die soon. My patch provides a
 reasonable transition behavior for existing users of the setting before it
 goes away completely.

 What do you see as inadequate about your pull request mentioned above, as
 a way to preserve CACHE_MIDDLEWARE_ANONYMOUS_ONLY? Why do you think it
 needs to go away completely, and/or be replaced by another setting?

 I understand that simply caching all requests is often fine, since the
 caching will vary by cookie anyway and won't result in the wrong content
 being shown to a user. But in some cases it's still useful to be able to
 easily turn off caching for all user-variable pages, since for some sites
 they may be the pages with the most dynamic content (and caching with
 Vary: Cookie eats up cache memory a lot faster).

-- 
Ticket URL: <http://code.djangoproject.com/ticket/13283#comment:19>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to