On Sat, Nov 26, 2011 at 4:07 PM, Addy Yeow wrote:
> If I use cache_page() decorator for my view function, will the TIMEOUT be
> able to take precedence over CACHE_MIDDLEWARE_SECONDS?
>
> In my settings.py,
>
> CACHES = {
> 'default': {
> 'BACKEND': 'django.core.cache.backends.filebased
u can test by yourself.
yes, i don't know the answer, neather
在 2011-11-27 上午12:08,"Addy Yeow" 写道:
> If I use cache_page() decorator for my view function, will the TIMEOUT be
> able to take precedence over CACHE_MIDDLEWARE_SECONDS?
>
> In my settings.py,
>
> CACHES = {
> 'default': {
>
If I use cache_page() decorator for my view function, will the TIMEOUT be
able to take precedence over CACHE_MIDDLEWARE_SECONDS?
In my settings.py,
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache',
'LOCATION': os.path.join(WEB_ROOT, "dja
> external event happening every 15 minutes that updates the original
> data Django processes; can Django be configured to give web clients
> the correct cache TTL? Example: the resource is regenerated externally
> at 11:00:00. At 11:00:01 a client accesses it and it should be given
>
o give web clients
the correct cache TTL? Example: the resource is regenerated externally
at 11:00:00. At 11:00:01 a client accesses it and it should be given
cache timeout up until 11:15:00, that is, 899 seconds. Client
accessing at 11:00:02 should be given timeout 898 seconds, and so on.
Then at 1
5 matches
Mail list logo