Hello,
In our application I must guarantee that user is logged only once to the
application.
I have the following problem.
1,User logged to aplication, create session1
2,User browser crased, but session1 is still alive for next 30minutes
(session expiration time is 30minutes).
3,User open new
Using a session listener to record session creation/destruction and them use
that info to invalidate previous sessions where the user is the same?
Ernesto
On Fri, Mar 6, 2009 at 11:34 AM, Martin Bednář martin.bed...@triax.czwrote:
Hello,
In our application I must guarantee that user is
Martin Bednář wrote:
Hello,
In our application I must guarantee that user is logged only once to the
application.
I have the following problem.
1,User logged to aplication, create session1
2,User browser crased, but session1 is still alive for next 30minutes
(session expiration time is
instead of storing a user id store a uuid that is generated on login,
and resolve the uuid back to user.
every time the user logs in you invalidate all other uuids they have
and generate a new one.
-igor
On Fri, Mar 6, 2009 at 2:34 AM, Martin Bednář martin.bed...@triax.cz wrote:
Hello,
In
