You are right, I will go with a DB field instead of HashMap solution. Thanks!
DNewfield wrote: > > "kkus" <[EMAIL PROTECTED]> wrote: >> In that listner, what is general >> problem if I provide a HashMap to >> store username and login count >> when login fails, and clear HashMap >> for that user when login suceeds? > > Forcing every login attempt for the entire application to synchronize on a > single datastructure? (And therefore diminishishing the ease of > distributing your app to multiple servers as well as losing the login > attempt info across server restarts.) Why not asynchronously store it in > the DB which is getting hit as part of the login anyway? > > -Dale Newfield > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/locking-account-afer-several-tries-of-login-tf2735347s2369.html#a7638188 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
