On Fri, Jun 11, 2010 at 3:13 PM, Tom Evans <tevans...@googlemail.com> wrote: > On Fri, Jun 11, 2010 at 11:41 AM, jjmurre <jan.mu...@gmail.com> wrote: >> Hi, >> >> I am using long living session in the database backend. Because of >> Robots I am getting a huge amount of sessions. I googled if there is >> some kind of Session middleware that does user-agent blacklisting and >> does not create new sessions in the database for Robots accessing the >> site. I did not find anything. Would this be possible at all? >> >> I could think of subclassing >> django.contrib.sessions.backend.db.SessionStore and only create some >> kind of in-memory Pseudo Session. I am afraid that I have to override >> almost all methods of SessionStore for that. >> >> Does anyone know of an existing solution for this problem? If not, >> would my proposed solution be the way to go, or are there better >> alternatives? >> >> Regards, >> >> Jan Murre >> > > Subclass django.contrib.sessions.middleware.SessionMiddleware, > overriding process_request. > Determine whether you should or should not initiate a session from the > request object, and if you should, call the super class's > process_request method. > Replace django.contrib.sessions.middleware.SessionMiddleware in > settings.MIDDLEWARE_CLASSES with your replacement one. > > Simples. > > Cheers > > Tom >
Hi Tom, Thanx for your help. That sounds like a very good approach. I assume I have to put some dict-like object on the request to avoid all kinds of attribute errors? Regards, Jan -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
