tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <Craig.McClana...@eng.sun.com>
Subject Re: Common Session code 3.3/4.0 (was: [VOTE] New Committer: Kief Morris)
Date Tue, 06 Feb 2001 22:18:26 GMT
cmanolache@yahoo.com wrote:

> > >( +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 sessions, although that would require sharing the Session interface. Maybe
> > a bit too much work for the current release cycle.
>
> This doesn't have to be part of tomcat3.3 release - it can be a standalone
> module. The only issue is that the code you write ( Store, impls, etc )
> need to be "standalone" - i.e. be usable in any container.
>
> ( the session manager for tomcat3.2 is based on early catalina session
> managers, but it was a huge pain to extract the session management and use
> it, since it depended on a lot of internals - Request, Lifecycle, etc).
>

You will find that several new things in Servlet 2.3 actually increase the
dependency on the container's notion of a Context -- for example, application event
listeners.  This can be done in many ways, of course, but at some level a completely
"stand alone" session implementation is an ideal, not a practical reality.

>
> With the same functionality, you can organize the code in many ways. If
> 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 it.
>

Is 3.3 ready to give up on JDK 1.1 compatibility?  If not, the extra effort to
maintain it is not particularly "productive" from a Tomcat 4 point of view.

>
> --
> Costin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-dev-help@jakarta.apache.org


Mime
View raw message