> Hello everyone,
>
> I am writing about an issue on invalidation of sessions.
> In the current implementation, a session is deleted from the Database when
> it is invalidated. Is this really the behavior expected?
I have been looking over the code some, and I think that behavior is
correct. I think the DB schema was written with the thinking that
that field may some day be useful when more than one instance of
Tomcat is handling requests.
> I mean, if there is an attribute to specify if a session is valid or not,
> a session that is invalidated should have this attribute reset instead of
> being deleted, isn't it? If this is not true, it is not possible to see
> difference between a session that is not valid anymore and a new one.
Once a session is marked invalid, my understanding is that it only
exists for the remaining scope of the page that marked it invalid.
I think if you have a page with 2 frames in it, and one of the
frames marks the session as invalid, the other frame might get;
* a valid session until it is marked invalid by the other page
or
* a new session
depending on the race condition of the browser and webserver loading
both frames.
Cheers,
-bob
> Can anyone tell me something about the plans for the implementation of
> this feature?
>
> Cheers,
> Daniel
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
Cheers,
-bob
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
