Hi Brian, We cannot use Hazelcast. In fact, at first we thought about it, but, as I mentioned, we are about to get CouchBase ready (it took some time to be ready for us because of external forces). Couchbase fits better for us than a distributed cache like Hazelcast though. We do need to work for some time with this MySql database, it's pretty much the best option we have for several reasons now.
It doesn't seem like the best option for us to develop a whole new app and get it to prod environments with just this single and tiny responsibility. Separating authentication, session management and so on from our actual app whose responsibility is that one seems more like a hack to me.. But I would like to understand the reasons why you're suggesting this. Have you had problems having SessionValidationScheduler working in a distributed app before? Could you tell me more about this? :) Thanks! -- View this message in context: http://shiro-user.582556.n2.nabble.com/How-does-SessionValidationScheduler-work-with-distributed-applications-tp7581469p7581471.html Sent from the Shiro User mailing list archive at Nabble.com.
