#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 mtredinnick):

 A few things here.

 Firstly, sorry that you got mail from somebody without the manners to
 understand how Open Source works. Unfortunately, that happens from time to
 time. Unpleasant, I agree.

 I don't really understand your argument about unlinking. We release the
 lock before unlinking and unlinking just reduces the link count, so the
 file isn't removed until the last user has gone away (and unlocked it
 first). So I don't quite see the failure mode you're talking about.

 Leaving 0 bytes files around is simply not an option. It will eventually
 fill up the directory's dirent records to the point that you cannot create
 any more files, which is very uncool. We can't replace one bug with a
 different one.

 I'll back out the patch, try to understand what's going on and possibly
 resurrect the "move" version, ugly as it may be. Since you do have a nice
 failing case, I'll attach the patch here when I'm done and get a thumbs up
 from you before it goes in. I couldn't repeat the issue yesterday at all.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8616#comment:18>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to