> Is there a recommended/preferred persistent ticket registry implementation > that works in both 3.4.7 and 3.5.0? Currently we need something as simple as > possible, e.g. no need for clustering support, minimal/no runtime setup or > maintenance, etc.
Persistent and simple is hard. Ehcache will persist cache items to disk on graceful shutdown, but I'm not aware of any feature that flushes all cache writes to disk synchronously. That's to say you'd be hosed if your Ehcache node died abruptly. Your best bet may be to simply use JpaTicketRegistry against MySQL or PostgreSQL. I encourage you to think about how much you need persistency. In our case we actually wanted to be able to forget about all tickets with one fell swoop in some cases, yet we have achieved a highly reliable ticket store using a pool of memcached nodes. I honestly think it doesn't get any simpler than memcached, and it's persistent enough for our needs. https://wiki.jasig.org/display/CASUM/MemcacheTicketRegistry M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
