Rod,
"Saving" sessions via a singleton wont work if they're swapped in and
out of memory (read: persisted) as you will have the same session
object by value but not by reference. Session persistence is a fairly common
thing nowadays.
A valid scenario for enumerating through all sessions is when you
need to shut down the service and clean up the sessions. Let's say
your application consists of EJB beans accessed by HTTP and non-HTTP clients
and you want to shut down the HTTP channel. "Clean" shutdown requires you to
invalidate() all active sessions so the listeners fire, at the very least. I
dont see this scenario being taken care of in 2.1 or 2.2 spec but perhaps I
am missing something.
Can someone (Mssr Davidson or other Sun people) care to comment?
Regards,
Alex.
Rod McChesney <[EMAIL PROTECTED]> wrote:
>The reason session enumeration was deprecated is that you could be
>exposing sensitive information if such is stored in the session. Out of
>curiosity, why do you want to display all the sessions this way?
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
