#8616: File-based sessions dropped with SESSION_SAVE_EVERY_REQUEST = True
----------------------------------------------+-----------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Status: assigned | Milestone: 1.0
Component: django.contrib.sessions | Version: SVN
Resolution: | Keywords: session, file,
race
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------+-----------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [comment:22 [EMAIL PROTECTED]:
> However, with my patch, the django-controlled lifetime of the lock files
was the same as the session file itself. I unlinked them in the delete()
method. So, the number of files would grow twice as fast as before, but
the growth would be linear. The only caveat I can think of is the one I
mentioned earlier: external session sweeper code that ignores the lock
file. I tried to mitigate this by purposely keeping the lock file name
very similar to the lock itself.
That last sentence should be "...very similar to the *session file*
itself."
--
Ticket URL: <http://code.djangoproject.com/ticket/8616#comment:23>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
