One of the strongest weaknesses we have in CAS today is the ticket cleaning process, as all tickets need to get deserialized, which could be a performance killer and is a memory hog (especially in rememberMe scenarios). Is it planned to enhance the ticket cleaning mechanism in 4.0 by not deserializing but using the lastTimeUsed timestamp and the ticket timeouts? Performing getTickets() on the ticketRegistry when cleaning is the culprit.
Robert -- 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-dev
