I might be wrong, but this does not seem like a Wicket related problem.
Here a spontaneous idea what I would try:
To track sessions of a user I would try to use a database table that
associates sessions with users and a boolean flag "isvalid".
A new session would have to create an entry in that table with isvalid
set to true and in the same transaction find all existing entries for
the same entries to set isvalid in those records to false.
For every request a session would have to check in that table if it is
still valid and if not invalidate itself and delete the record (probably
best done in onBeginRequest of IRequestCycleHandler). Also when a
session times out the corresponding record has to be deleted (probably
best done in sessionUnbound in WebApplication).
Not sure if that is the best way, but at the moment that is the only way
that comes to my mind. Hopefully this gives you an idea where to start.
Cheers, Chris
The Sanity Resort <http://sanityresort.blogspot.com/>
Am 03.10.2011 16:00, schrieb [email protected]:
Please provide your advice about what is the easiest way to identify the
second time user login for same user.
User login in one machine and one session is created.
User go to another machine and login again. The system create a another
session for the same user and there are two sessions associated with the
user.
What is the best way to identify the second time login for this user and
kill the first session? The application has Wicket Page and Ajax page or
link also.
Thanks in advance.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/What-is-the-right-way-to-identify-the-second-login-for-the-same-user-tp3867590p3867590.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
