We have been users of the Memcached Ticket Registry for a few years now (Current Production CAS is v4.0.4). I am currently looking to upgrade our CAS implementation to v5.0.x and when implementing the memcached registry in my test environment, I am getting a lot of inconsistences that do not resonate well with me. I've polled this mailing list and there hasn't been any response on the errors I'm receiving. That means I'm looking towards another avenue on our ticket storage. We have 4 CAS nodes, so a shared or replication instance must be used.
I'm curious to know what you are currently using and why does it work for your implementation? Cheers, -Jeremy ________________________ Jeremy Wickham Senior Systems Analyst Mississippi State University [email protected]<mailto:[email protected]> -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/46776a85ab1041d18dccaa87203a3494%40mail04.ad.msstate.edu.
