On Tue, Dec 22, 2009 at 3:14 PM, Victor Loureiro Lima
<victorloureirol...@gmail.com> wrote:
> You can purge the cache whenever you need and update it accordingly.

another strategy is to use the most volatile data as part of the cache
key.  that would ensure that new data would ask for inexistent cache
entries.  the old ones would eventually expire.

for example, if your records are never modified, but instead you add
new to replace the old ones, then your cache should be keyed on the
record ID.

it's not as generally applicable, but when possible, allows for big
simplifications of the cacheing layers.

-- 
Javier

--

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


Reply via email to