[EMAIL PROTECTED] typed the following on 02:07 PM 2/6/2001 -0800
( +2 if he also ports them to tomcat 3.3 or makes them independent of
the container architecture - i.e. general purpose utils for
serialization/deserialization with a simple adapter for each server :-)
Sure, the 3.3 code could
[EMAIL PROTECTED] typed the following on 09:44 AM 2/6/2001 -0800
Kief has recently proposed improvements to the session management code
in Tomcat 4, and wants to continue helping out. I hereby propose him as
a committer on the Tomcat project. Votes, please?
+1
( +2 if he also ports them to
( +2 if he also ports them to tomcat 3.3 or makes them independent of
the container architecture - i.e. general purpose utils for
serialization/deserialization with a simple adapter for each server :-)
Sure, the 3.3 code could be modified to use the Store interfaces to serialize
its
you look at tomcat.util you'll find that none of the tools there depends
in any way on any tomcat internal object. If the store can be written as
a general-purpose utility, and you keep container-dependent code in a
small adapter then more people will be able to use it or contribute to
--- [EMAIL PROTECTED] wrote:
IMHO it would be a mistake to write a session
manager using the same
abstractions as in a servlet container - after all
the task is to store
data and the requirements are pretty specific )
I'd like to poke my $.02 in and say I totally agree
with Costin.
