> Retrieving that information can be very expensive for anything other than > the JPA and In-Memory mechanisms, and in some cases impossible without > actually explicitly storing that information (i.e. Memcached).
Can you explain why MemCacheTicketRegistry#getTickets() isn't supported? I can't imagine any fundamental reason that a cache system wouldn't support some kind of iteration as needed here. That's not to say that Memcached does in fact support iteration over cache entries, but that it ought to. I would like to see a query API be exposed by the ticket storage components to support use cases like this. Is a query interface to SessionStorage a reasonable feature for 4.0? 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
