Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Sender: arkin@arkin.exoffice.com
Message-ID: <38766F30.7272E8B@exoffice.com>
Date: Fri, 07 Jan 2000 14:56:48 -0800
From: Assaf Arkin <arkin@exoffice.com>
Organization: Exoffice
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: Cleanup: sessions
References: <3876473D.E10BF155@eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> 
> - The SessionManager is _required_ to respect the APIs. Any parameter
> that
> is defined by the deployment descriptor will be specified and set up in
> Context.
> SessionManager tuning can be done for things like database persistence,
> etc.

Beautiful.

> 
> - SessionInterceptor ( the default == the current code ) will call the
> session
> manager of the current context ( and it will be called after the context
> 
> is determined ). Feel free to use a different Interceptor if you don't
> like
> this model. ( for example Apache may send the session id, and your
> interceptor may use a different internal API to mark it as accessed ).
> A session interceptor is _required_ in order to mark as accessed the
> session ( user doens't have to call getSession() ).

Makes a lot of sense. (I have an itch for doing session persistence :-)
)

arkin


> - Internally, tomcat.core will use HttpSession. Your manager can
> cast to it's internal implementation ( and it's guaranteed that accessed
> 
> will receive the object generated by getSession()).
> 
> Let me know what you think, I'll check in later today or tommorow.
> ( also - read Craig's Tomcat.Next - he's much better at explaining!)
> 
> Costin
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org