On Wed, May 9, 2012 at 4:48 AM, Odilo Oehmichen <odilo.oehmic...@gmail.com>wrote:
> Hi, > > CAS 3.5 will support an EhCache solution for the ticketregistry (see [1]). > That's nice. > > I have two questions concerning the implementation: > > <snip /> > > 2. There is an overlap between the ExpirationPolicy configured for a > ticket and the > eviction policy (aka timeToLive) configured with the EhCacheFactoryBean. > Is that right? > > Pretty much all of the distributed ticket registries will have this contention between their own configured policies and the actual expiration for the ticket. Unfortunately, most of the distributed implementations cannot delegate to anything in the actual tickets themselves to determine expiration and thus must rely on their own methods for clean up [the notable exception being the JPA-version]. Cheers, Scott > Thanks > Odilo > > [1] https://wiki.jasig.org/display/CASUM/EhcacheTicketRegistry > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
