1👍
If you delay response in threaded server, your service will be prone to DOS-attack. Attacker may send may requests at once, and all your threads will sleep at once…
You should better to ask CAPTCHA if there are too many attempts from same IP.
Upd: I would use Twisted (or Tornado, but I never used it) and nginx (not Apache) as frontend. You may even use both Twisted and Django, but you will have to write code that imitates Django auth and session with Twisted, writing proper data into database.
1👍
Downvote me if I’m wrong, but I think each thread only processes one request at a time. Thus, if you want a slow request, just do a time.sleep in that thread and the server will take a longer time to process it without affecting the other concurrent requests.
- [Answered ]-MemoryError at … No exception message supplied
- [Answered ]-Django class-based-view access context data from get_queryset
- [Answered ]-Django models with external DBs
- [Answered ]-How do I turn my urls into readable names?
0👍
Http is a stateless protocol. The only way to connect requests is to store the session information somewhere client side. Since you cant control client behavior, the best chance is to log failed login attempts on the serverside and delay login routine for those accounts.