Sessions don't always get destroyed by the filter (i.e. they become invalid
beforehand or someone doesn't log out of CAS).  The Listener handles that
situation.

-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia


On Wed, Nov 26, 2008 at 8:56 PM, qingfeng zhang <[EMAIL PROTECTED]>wrote:

> Hi,
>
> I'm reading the code of Single Sign Out part and I don't understand the
> function of SingleSignOutHttpSessionListener.
>
> The SingleSignOutFilter will destroy session and remove it from the map of
> managed sessions, why we still need to detect the sessionDestroyed event?
>
> Thanks & Best Regards,
> Qingfeng Zhang
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to