-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 lb,
lightbulb432 wrote: > > > Christopher Schultz-2 wrote: >> I would argue that autodeploy doesn't help much in this case, but we'll >> stick with that assumption for this discussion. > > I realize it wouldn't help for things like database changes, but what about > changes to the structure of the HttpSession map, or the cookie structure, or > something that has to do at the web application? I just meant that auto-deployment doesn't really help with uptime. I'm not sure I understand your follow-up question. >> I'd start with org.apache.catalina.StandardContext (and, specifically, >> the "reload" method), since that's the thing being reloaded. > > Where could I find the code where Tomcat stores its definitive list of all > the current, active HttpSessions? (Where's the structure that Tomcat adds a > newly created HttpSession to, and from which it removes timed-out or > invalidated HttpSessions, and the code that manipulates it?) You should just download the code and start looking around. It's not hard to follow the action starting from what happens when the request has getSession() called. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG7+v39CaO5/Lv0PARAjpaAJ9qSQj2cPj/8Fkq4x0m/jDVdwMNUQCfUCKX zbmwNMNJxlZs3lNXwtXS7+M= =K2AX -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
