On 1/9/07, David Cramer <[EMAIL PROTECTED]> wrote:
> Using full page caching, or view caching, is not an option for us on
> most pages, as things vary such as moderation options.
There are still plenty of ways you can make use of the cache. From
what you've said, I think two in particular are worth looking at:
1. It'd be pretty easy to write a template tag -- say, {% cache %}{%
endcache %} -- which caches all the nodes within itself; this way you
can isolate parts of the template which hit the DB, and cache those
results without having to cache the entire rendered template.
2. If you have a significant number of users who browse while not
logged in, the CACHE_MIDDLEWARE_ANONYMOUS_ONLY setting will just cache
everything they see, no questions asked.
I'm not saying that you shouldn't necessarily try to cut the number of
data accesses going on in your templates, it just seems to me that
there are a lot of options to explore which don't involve lots of time
spent rewriting Django's template system...
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
