> 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).
That's one of many pain points. We're tracking improvements to the SSO session storage subsystem on https://issues.jasig.org/browse/CAS-1421, which is definitely a CAS 4.x or 5.0 scope feature. Fixing this problem and other related ones will require some fairly substantial API changes throughout the codebase. 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-dev
