I should pause in that situation, where two different JSESSIONIDs for the same user account Exist. Or, 2. Two tabs of the same browser referenced the same JSESSIONID. Any suggestions? If an existing session is detected, users either: a) Leave the second attempt b) Kill the current session (an assassin!) And start a new session. The priority is to have an individual side measure. That is, I do not want to rely on user's turnkey cookies which compel JSESSIONID to the user. "post-text" itemprop = "text"> Part 1 can be done using a singleton pattern that checks the current session for the user against the user-SID map is. Part 2, which can be understood in the Transactional WebAP, where you need to make sure that the user reads the correct information (instead of a tab with old values and a tab with the new tab). .. It can use the same session map, it can be injected into the dome and validate it using javascript. Edit. Part 2 verification can be improved in a filter against a client-session map and guarantees a correct definition of the object that a real unique singleton example exists.
Comments
Post a Comment