On Oct 7, 2009, at 12:35 PM, kmike wrote:
> 1. Maybe you can use django's Vary support (
> http://docs.djangoproject.com/en/dev/topics/cache/#using-vary-headers
> ).
Thank you! The method I came up with was to use the fragment-caching
facility with the language code as one of the keys, which
> appropriate cache_prefix function
oops, key_prefix, not cache_prefix :)
On 8 окт, 01:35, kmike wrote:
> 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.
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/k
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/km
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 re
5 matches
Mail list logo