I am curious why the entire engine is placed in session. I understand that much of it is transient, but something just doesn't make sense to me. I've been wondering about this for a while, but let me just make sure I have it straight (this is from memory, so please correct if I'm way off):
- the servlet holds an engine pool - each engine has a page pool (not sure why the page pool wouldn't just be in the servlet, not sure why you need so many page pools (e.g. if there is more than one engine in the engine pool)) - engines are returned to the pool unless a session has been created (a visit or page recorder is used), whereupon that engine is added to session - when the session invalidates, the engine is returned to the pool (or just gets garbage collected if the user "disappears", not sure if this will happen unless engine pool uses weak refs) Just curious as to the design principles involved. Wondering if this is just a side effect of an initial design decision that has stuck around. -C Protect yourself against identity theft with Equifax Credit Watch. Visit http://www.creditalert.equifax.com. This message contains information from Equifax Inc. which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail [EMAIL PROTECTED] _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
