#8616: File-based sessions dropped with SESSION_SAVE_EVERY_REQUEST = True
----------------------------------------------+-----------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: reopened | 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:14 anonymous]:
> As I think more about this, unlinking the lock file creates yet another
race condition. The whole point of the lock file is that it is a shared
locking context. Having each request unlink it destroys the shared
context and may create the situation where there are several lock file
handles in existence at once with only one of them being linked to the
lock file name on the file system. How this is causing my session data to
be lost is beyond me.
>
I mis-spoke. The situation I was thinking about is where several lock
*files* exist because they are open but another thread/process has
unlinked them. I don't know enough about how the low-level I/O works to
know if this is a possibility.
--
Ticket URL: <http://code.djangoproject.com/ticket/8616#comment:16>
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
-~----------~----~----~----~------~----~------~--~---
