Also attach some HttpSessionListener to your web application in order to remove old sessions from the database whenever they get destroyed and prevent that table for growing without control.
Jeremy Thomerson-5 wrote: > > Store the session ID in your DB whenever someone signs in. Then if > someone signs in, and the session ID is not the same, you can either > block them from signing in, or you can have something in the request > cycle that checks on every request to make sure that this session ID > is still allowed to be signed in. If it's not, sign out. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > > On Fri, Jun 12, 2009 at 12:30 PM, tubin gen<[email protected]> wrote: >> I need suggestions on implementing single user login , like My system has >> a >> user with a username jdavid and my application should not allow two >> different sessions for the same username jdavid , can one session peep >> into all other session >> to see if the any has a usernaem jdavid, I am basically looking for some >> pattern if any available for restricting multiple session for the same >> username . >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/how-to-avoid-multiple-session-for-the-same-username-tp24003169p24003587.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
