Brian Demers wrote > If you want to use Tomcat (or other servlet container’s sessions) use > ‘ServletContainerSessionManager’ instead: > > https://shiro.apache.org/static/current/apidocs/org/apache/shiro/web/session/mgt/ServletContainerSessionManager.html
You are right Brian but from one side we don't want to compromise future benefits related to generic (i mean not container specific) clustering or enterprise-caching configurations. On the other side we appreciate the single configuration point of the shiro.ini file; using container's sessions means using tomcat specific configuration options in context.xml. We would have the cake and also eat it. Anyway, the purpose of my questions is only to understand if there is a chance to use Tomcat's parallel deployment in conjunction with Shiro's native sessions, or/and maybe to obtain some advices in order to achieve our goal. Any thoughts? In our webapp, we make use of websockets and current implementation is able to associate multiple websockes channels (eg. in case of two browser tabs) to the same session of the logged user. If eventually we decide to go back to ServletContainerSessionManager, could we have some problems or something to keep in mind with this kind of situation? Thank you, Matteo -- Sent from: http://shiro-user.582556.n2.nabble.com/
