Maybe you could have a hashtable in the ServletContext that maps loginId
to HttpSession -- then use a HttpSessionListener to listen for session
creation -- when the session is created look for a value in the hashmap
in the servlet context -- if it is there then invalidate the mapped
session. Then add (put) the new mapping into the hashatable.
Ricardo Andres Quintero wrote:
Hello Guys
I need not to let users to login in my app simultaneosly.
I mean if a login-password is actually logged in, i need to
invalidatye that session and then let the new login-password
to work in, after invalidating the old session.
Any ideas? and of course any examples?
--
Ricardo Andrés Quintero R.
Ubiquando Ltda.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
