1. Maybe you can use django's Vary support (
http://docs.djangoproject.com/en/dev/topics/cache/#using-vary-headers
). This
will work if you have language preferences in http headers. If you
only set language cookie (or store language preferences in sessions)
then you can use http://bitbucket.org/kmike/django-view-cache-utils/
for that (writing appropriate cache_prefix function).

2. Functions (from the same django-view-cache-utils app) that removes
page from cache based on page's url (and
possibly key_prefix):

http://bitbucket.org/kmike/django-view-cache-utils/src/tip/view_cache_utils/__init__.py#cl-59

On 8 окт, 00:11, Christophe Pettus <x...@thebuild.com> wrote:
> Chatting with a client last night, two Django cache-related questions  
> came up...
>
> 1. Is there any convenient way of using the @cache_page decorator  
> while caching separate versions by language using the Localization  
> facilities?  It seems that it will cache the first access, and return  
> it regardless of language.
>
> 2. Is there a way of invalidating the cache, for example if the  
> underlying database gets an update?
>
> Thanks!
> --
> -- Christophe Pettus
>     x...@thebuild.com
--~--~---------~--~----~------------~-------~--~----~
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 
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