you can inherit the cache system (UpdateCacheMiddleware, FetchFromCacheMiddleware) with your own get_Cache_Key function that you extend by layout (as you hopefully do not 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 message: >date: 13.07.2011 08:08:31 >from: "het.oosten" <het.oos...@gmail.com> >to: "Django users" <django-users@googlegroups.com> >subject: [<django-users.googlegroups.com>] Re: session and caching > > > > >> 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, doesn't show >up, therefore I doubt now if @vary_on_headers is the right option for >me. > >-- >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. > -- 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.
