What about having the session store stuff used also in
Tomcat 3.2 / 3.3 . 

It seems to be a fine candidate to jakarta-commons ...


-
Henri Gomez                 ___[_]____
EMAIL : [EMAIL PROTECTED]        (. .)                     
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-----Original Message-----
>From: Bip Thelin [mailto:[EMAIL PROTECTED]]
>Sent: Friday, April 20, 2001 9:02 PM
>To: [EMAIL PROTECTED]
>Subject: Store Proposal
>
>
>We've had some issues with the background threads, expiration 
>and stuff so I
>migrated some of the common stuff into a StoreBase and had 
>JDBCStore and FileStore
>extend it and have the opportunity to implement it's own 
>processexpires and some
>other methods. The code is attatched. I've also implemented an 
>extended table for
>JDBCStore, there still remains some work on using the extended 
>fields when checking
>expiration and loading I'll have that done soon. This is what 
>a table for JDBCStore
>now should look like:
>TABLE [tomcat$sessions] (
>       [id] [varchar] (100) NOT NULL ,
>       [data] [varbinary] (1000) NULL ,
>       [valid] [char] (1) NOT NULL ,
>       [maxinactive] [int] NOT NULL ,
>       [lastaccess] [numeric](18, 0) NULL 
>)
>
>Here's how you can configure the table and column names:
>
><!--Store className="org.apache.catalina.session.JDBCStore" 
>driverName="SQLDriver" 
>connectionURL="jdbc:protocol://server?user=;password="
>sessionTable="tomcat$sessions" sessionIdCol="id" 
>sessionDataCol="data" sessionValidCol="valid" 
>sessionMaxInactiveCol="maxinactive"
>sessionLastAccessedCol="lastaccess" debug="99"/-->
>
>
>       ..bip
>

Reply via email to