On Thu, Dec 17, 2009 at 6:47 PM, Luke Plant <[email protected]> wrote: ... > The problem with signals is that they don't return values, and so the > mechanism can't interact with the actual login process. It can only > notice that something is going on and try to stop it by some external > mechanism.
Actually, they do return values -- an iterable of (receiver, response) pairs. Otherwise, I agree with most of your sentiment. But -- I would like to see some form of rate limiting built in; Django tries to do the right thing wrt. security, and brute force is a common form of attach. -- 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.
