E.G. if you want to implement a session monitor. Depending on the kind of information you want to display it gets at sime point annoying to to copy everthing from the session to a store and to remove it from the store when the session ends. - More code = more possible error, less perfomance - More memory = less performance
Even if you do it, the problem of the original poster is the same. Now he has a Vector of SessionInfo objects that have to be persisted if the server is shut down. The other option is to recreate the Vector on the SessionActivated event (don't nail me on the exact name I don't have that at hand) which is fired each time when a session is recreated from a persistent store. BTW.: I just act as an advocat in this case, personally I have never felt the need to do that, as we store everthing that we need from a session in the database. > -----Ursprüngliche Nachricht----- > Von: Shapira, Yoav [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 14. August 2002 15:18 > An: Tomcat Users List > Betreff: 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 > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
