Hi, This could be done as an optional configuration with a hardcoded default of 10000. Since no configuration change is necessary to retain original behavior, than would this still qualify as a feature change?
I think I will weigh in on one aspect of this as I have run into this problem before. The side effect is as you describe until traffic increases further. At that point, users may not be able to login successfully until traffic subsides. "Minor issue" could be relative. peace, Ryan McIntosh Software Architect PeaceWorks Computer Consulting ph: (204) 480-0314 cell: (204) 770-3682 r...@peaceworks.ca ----- Original Message ----- From: "Tim Graham" <timogra...@gmail.com> To: "Django developers" <django-developers@googlegroups.com> Sent: Tuesday, 8 February, 2011 08:48:09 GMT -06:00 US/Canada Central Subject: Design design needed: #14093 - Unable to create a new session key on higher traffic Hi, I wanted to raise this ticket for discussion as to what the best solution might be. As suggested in the ticket, I think adding a setting to control the number of cache attempts instead of hard-coding "10000" might be a reasonable approach. I'm not sure if that solution would be considered a "feature addition" (adding a new setting) and thus not appropriate for this stage of the release cycle. Has anyone else experienced the issue and devised a workaround? It's a minor issue since the side-effect seems to be that the login silently fails and a user must retry. Thanks, Tim -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
