I've restored the previous version. MaybeAt 11:02 PM 9/20/2004 +0000, Jan.Luehe wroteSessionEvent.getData() could have differentiated between session expiration and session invalidation, so we would not have to determine the cause of the SESSION_DESTROYED_EVENT by comparing getLastAccessedTime() and getMaxInactiveInterval()?
It would be great if SessionEvent.getData() could do that. I looked into it a bit and I think the problem would be Session.expire() doesn't take a parameter that would allow calling code to indicate whether the expire call is due to timeout or an HttpSession.invalidate() call by the application. I expect it would be easy enough to find a way around this for StandardSession, but it would break for anyone who for some reason implemented Session themselves :(
Thanks much!
Brian
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
