codekoala/django-axes — pull request #8 by MikeSandford (2011-10-11 19:55:05+00:00)
Title: Could I get some feedback on this modification?

Since this changes the database model and the amount of state that comes with the application I don't expect that it will get pulled. But I'd like to get your feedback on it. Also, if I should change the name of the fork to avoid confusion, I'll do that too.

Also I mentioned at the bottom of the commit message that I'm getting double entries on admin login, success or failure. It's really puzzling me. It seems like the middleware might have something to do with it, but I don't know enough about middleware to really track the problem down. If you've got any tips I'm all ears.

=================================
It's extremely helpful to me to track all logins.
This patch makes that happen, while preserving all
the functionality of the original django-axes.

Instead of only logging failures, it logs all
access attempts and sets a status on each one
to keep track of success/failure/lockout.

Right now I am getting the correct single record
per regular login, but two records per admin
login. Any ideas?