As always afterwards everything is very logical :-)
Never used caching before.
--
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
dja
want to cache every
> single user, but all user using the same layout)
> > Then create a new middleware, that uses your both new created
> CacheMiddlewares. See django.middleware.cache.py
> >
> >
> >
> >
> >
> >
> >
> > >reply to messa
>
>
>
>
>
>
>
> >reply to message:
> >date: 13.07.2011 08:08:31
> >from: "het.oosten"
> >to: "Django users"
> >subject: [] Re: session and caching
>
> >> Are you sure because in the docs I find the opposite.
>
>
created CacheMiddlewares.
See django.middleware.cache.py
>reply to message:
>date: 13.07.2011 08:08:31
>from: "het.oosten"
>to: "Django users"
>subject: [] Re: session and caching
>
>
>
>
>> Are you sure because in the docs I find the opposite.
> Are you sure because in the docs I find the opposite.
>
When I read it correct this is about caching the session. I was
referring to (or trying to) caching the entire webpage using a custom
session key for the lay-out (I use memcached)
When I look at the request headers my custom session key,
> I have site with with a lay-out depending on a session, set in my
> view. I first tried site-wide caching, and this obviously didn't work.
> The caching is not session aware, and the lay-out changes almost
> randomly.
Are you sure because in the docs I find the opposite.
https://docs.djangopr
I have site with with a lay-out depending on a session, set in my
view. I first tried site-wide caching, and this obviously didn't work.
The caching is not session aware, and the lay-out changes almost
randomly.
Therefore I tried my luck with the @vary_on_headers decorator, using
my session variab
7 matches
Mail list logo
