Originally posted by Rahul Bhattacharjee:
There is a host hearder in the HTTP request , that might help to identify a host.
Originally posted by vinod perla:
Adeel Ansari thank you very much for the response. What you said is right I actually want to know the client. Is there a way to identify the client uniquely even when a firewall is enabled?
Originally posted by vinod perla:
Actual Requirement:
If a user already logged in system1 and if anybody tries logging in with the same user account in system2, an alert should be prompted saying 'A user already logged in with the same details. Do you want to terminate it or not?' Basing on its input the system should either terminate the session of the user in system1 or it should just take the user in the system2 to the login screen again.
If same thing is tried in the same system the alert shouldn�t show up and the system should allow to login
Block the login if the user is already logged in to the system and some other user or the same user try to log in to the system using the same login credentials.
Originally posted by vinod perla:
Thank you for the response. Is there a way to know whether a user has already logged in?
Originally posted by Adeel Ansari:
HOST field wouldn't help here. If you make a request to "http://www.javaranch.com" then the HOST would be "saloon.javaranch.com".
[Edited]
Host - Header Field Definitions
Actual Requirement:
If a user already logged in system1 and if anybody tries logging in with the same user account in system2, an alert should be prompted saying 'A user already logged in with the same details. Do you want to terminate it or not?' Basing on its input the system should either terminate the session of the user in system1 or it should just take the user in the system2 to the login screen again.
If same thing is tried in the same system the alert shouldn�t show up and the system should allow to login
Micheal John
SCJP 1.4 (86%), SCWCD 1.4 (86%), SCBCD 1.3 (85%), SCDJWS (Just Started...) - Satisfaction Lies in Our EFFORT, Not in the ATTAINMENT
There is always Something!
Actual Requirement:
If a user already logged in system1 and if anybody tries logging in with the same user account in system2, an alert should be prompted saying 'A user already logged in with the same details. Do you want to terminate it or not?' Basing on its input the system should either terminate the session of the user in system1 or it should just take the user in the system2 to the login screen again.
If same thing is tried in the same system the alert shouldn�t show up and the system should allow to login
Originally posted by vinod perla:
I should not use the DB either for the flagging.
Originally posted by vinod perla:
In this scenario which is the best way to keep track whether a user has logged in already? Suggest me some best way to handle the requirement.
Originally posted by Adeel Ansari: Why
Originally posted by vinod perla:
The requirement is to be fixed at the web layer as I was strictly suggested not to use any DB. I can use servlets, files to hold the user info, cookies, session and whatever possible from the web layer.
"Database is a collection of files."
Originally posted by vinod perla:
The Web servers are clustered and the session variables are not shared across web servers.
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |