I think Adam is talking about the sharing and distribution of PGTs on the client side for which there are ehcache and memcache implementations available when the app is clustered. There is no implementation yet available that is based on hazelcast for the client.
-----Original Message----- From: Paul B. Henson [mailto:[email protected]] Sent: Friday, January 23, 2015 1:38 PM To: [email protected] Subject: RE: [cas-user] CAS Client Proxy distributed cache size > From: Adam Causey > Sent: Friday, January 23, 2015 7:07 AM > > I originally was going with ehcache since there is a TicketStorage > implementation already available, but then realized how easy it would > be to create my own Hazelcast version. I'm not sure what you mean about creating your own version? I am using the unicon implementation: https://github.com/Unicon/cas-addons/wiki/Configuring-HazelcastTicketRegistry -- Paul B. Henson | (909) 979-6361 | http://www.cpp.edu/~henson/ Operating Systems and Network Analyst | [email protected] California State Polytechnic University | Pomona CA 91768 -- 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 -- 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
