Quinton, I'm curious about your thoughts on how the Servlet API's HttpSessionActivationListener [1] ties in with TurbineSessionService. SessionListener implements only HttpSessionListener, the callback for session creation and deletion events. When active sessions which have been serialized to disk during servlet container shutdown are loaded during a server restart, it seems unlikely that they will again show up in Turbine's list of active sessions. I'm currently working with a version of TurbineSessionService in SourceCast (I dumped our custom code which did the same thing so that we could share the maintainence costs). Any ideas in regard to the HttpSessionActivationListener issue?
- Dan [1] http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/http/HttpSessionActivationListener.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
