Nope, I did not enable the auth middleware.
Here are my 3 middleware components:
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.locale.LocaleMiddleware',
On Mar 9, 3:07 am, Alex Gaynor <[email protected]> wrote:
> Are you using the auth middleware? If so it will be hitting the
> session each query, even if your stuff doesn'tm
>
> Alex
>
> On 3/8/09, Dennis <[email protected]> wrote:
>
>
>
>
>
>
>
> > Memcached-backed sessions seemed to be created, even when the session
> > is not written to.
>
> > This is what I'm finding when I look at my memcache after hitting a
> > page that does not use sessions.
> > Thus, if an app uses sessions (but not much), memcache will fill up
> > with empty sessions.
> > (the same thing might happen with database-backed sessions, but I did
> > not check that).
>
> > Just wondering if there is a reason why session creation is not lazy
> > and only created when needed.
>
> --
> "I disapprove of what you say, but I will defend to the death your
> right to say it." --Voltaire
> "The people's good is the highest law."--Cicero- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---