Bear Bibeault wrote:You can;t do that just with the session because each client will gets unique session and they cannot be cross-checked.
You'll either need to keep information in the application context to check against, or perhaps even in the DB.
sorry for uppercase letter writing my humble for elaborate the concept behind your idea . means let us suppose we has a table current_user
which has field user_id , application_id , session _id ,
and the sessionid is generated from container when user A is login for their user_id and this information is save in this table like this
test , school, jsesso12345 ,
m

eans when user is login then we can check it for user_id exist or not in that table but my doubt is that when the second time user is login then this user_id is already exist for same user so how can he will be able to login for the second time .
please suggest me
thanks and sorry for uppercase