Hi, Mark. To give my own 2 cents, I use a session listener for exactly the same issue: Get information how many sessions are active, who is logged on etc. Currently my application struggles with a memory leak, and I suspect the vector not being cleaned up thoroughly (my problem :-( ).
Hiran ----------------------------------------- Hiran Chaudhuri SAG Systemhaus GmbH Elsenheimerstra�e 11 80687 M�nchen Germany [EMAIL PROTECTED] Phone +49-89-54742-134 Fax +49-6151-9234-5134 > -----Original Message----- > From: Mark O'Driscoll [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 14, 2002 3:21 PM > To: Tomcat Users List > Subject: Re: How to keep track of sessions > > > I am using the sessions to keep track of who is logged on, > for how long and > what they have done. Obviously there are other non servlet > ways to do this > but as tomcat gives the opportunity to track sessions, I > thought I'd use it. > Session persistence highlights a 'hole' in the > sessionListener interface. > > BTW: I'm surprised you think sessions should not be > persisted. I think it's > cool! > > Thanks for the help. > ----- Original Message ----- > From: "Shapira, Yoav" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Wednesday, August 14, 2002 2:17 PM > Subject: RE: How to keep track of sessions > > > Howdy, > > >> > >> Sessions are not meant to be persisted across server restarts. > >> > > > >Obviously other people have other opinions about that. > > Which is why I still suggested a solution I've used in the past ;) > > Even though I disagree with the approach of persisting someone else's > proprietary internal objects, I assume that whoever asked the question > has a reasonable and well-thought out cause, so I try to help. > > I'm still unclear as to why one would want to save the session object > itself, as opposed to only the parts of interest from it. > Does it have > to do with load-balancing, wanting to somehow augment / superimpose on > the built-in mechanism? > > Yoav Shapira > Millennium ChemInformatics > > > > -------------------------------------------------------------- > -------------- > ---- > > > > This e-mail, including any attachments, is a confidential business > communication, and may contain information that is > confidential, proprietary > and/or privileged. This e-mail is intended only for the > individual(s) to > whom it is addressed, and may not be saved, copied, printed, > disclosed or > used by anyone else. If you are not the(an) intended > recipient, please > immediately delete this e-mail from your computer system and > notify the > sender. Thank you. > > > > > > > -------------------------------------------------------------- > -------------- > ---- > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
