On Mon, 24 Jun 2002 [EMAIL PROTECTED] wrote:
> Date: Mon, 24 Jun 2002 16:34:12 +0200
> From: [EMAIL PROTECTED]
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: JDBCStore implementation
>
> 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?
>
What purpose would be served by leaving the expired session in the
database? There is no API that would let a servlet retrieve that data
again, so wouldn't it just clog up the disk?
> 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.
>
Identifying a new session versus an old (but still active one) is a
different question. The in-memory session manager knows this by noting a
difference between the created time and the last accessed time (which is
updated via a call to access()). It looks like JDBCStore isn't saving the
created time, or the value of the isNew flag, so there's no way to know
when the session is reloaded -- that sounds like a reasonable enhancement.
> Can anyone tell me something about the plans for the implementation of
> this feature?
>
Best way to ensure that this gets done eventually is to submit an
enhancement request to the bug tracking system:
http://nagoya.apache.org/bugzilla/
> Cheers,
> Daniel
>
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
