On Mon, Dec 21, 2009 at 12:52:24PM -0200, Victor Loureiro Lima wrote:
> Well, template caching invalidates view cache right? Plus, my understanding
> of the template cache is that
> it will hit my view, do all the DB stuff, but skip the template processing
> which takes a while to finish, is my un
2009/12/21 David De La Harpe Golden
> On Thu, Dec 17, 2009 at 03:54:02PM -0200, Victor Loureiro Lima wrote:
> > Okay, let me further explain my problem...
> >
> > My website depends heavilly on the caching system, I'm using cache_page
> to
> > cache my view ( using memcached backend ),
> > howev
On Thu, Dec 17, 2009 at 03:54:02PM -0200, Victor Loureiro Lima wrote:
> Okay, let me further explain my problem...
>
> My website depends heavilly on the caching system, I'm using cache_page to
> cache my view ( using memcached backend ),
> however I have the "Hello, " on top of every page when
Okay, let me further explain my problem...
My website depends heavilly on the caching system, I'm using cache_page to
cache my view ( using memcached backend ),
however I have the "Hello, " on top of every page when the
user is logged, thus I cant just cache everything.
So I began experimenting
Victor Loureiro Lima wrote:.
> auth system is in fact invalidating my current session id cookie, but
> afterwards it sets a new session id cookie, why does it do that?
>
Um. So that anonymous users of your site still have sessions? Django
supports "anonymous sessions", sessions and auth are diffe
I have a question about django's session/auth system and its logout method.
Whenever I want to invalidate a user session ( i.e.: calling
auth.logout(request)), django
auth system is in fact invalidating my current session id cookie, but
afterwards it sets a new session id cookie, why does it do tha
6 matches
Mail list logo
