On Wed, Feb 9, 2011 at 12:08 AM, Ryan McIntosh <[email protected]> wrote: > 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.
If a configuration item is necessary to avoid a bug, my feeling is that it could still come under the category of bugfix, rather than feature addition. However, my concern here is that for any value of N, there will be some level of traffic that will render that N insufficient. I'm not fundamentally convinced that allowing N to be configurable will actually fix the problem. I'd be much more interested in seeing a genuine attempt to fix the problem, rather than just paper over it a little more. Of course, I haven't given any thought to what that fix would look like... Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
