SessionData provides a solution to keep objects in the session, but a few problems (to my eyes) remain :
1 ) Session data is shared across the whole application and no mechanism is provided to clear in one instruction a set of data related to a common business act while keeping the other data in session. In some other frameworks, session data is on a per business act basis. The same functionality can be implemented with SessionTool, but it's up to the developer to code it. Session data contains the state of the user session and this state may be complex. What are the best practices as regards this point ? 2 ) In some cases, a load balancing on a per request basis may be required, and SessionData is then a (small) problem. The solution is either to save SessionData in a database table or to implement a serializable interface and to serialize through tomcat-replication.jar for instance. Lo�c On Thursday 30 October 2003 11:08 pm, Scott Eade wrote: > Eric Pugh wrote: > >This question comes up periodically.. If someone has a nice pulltool they > >would like to donate for 2.4 that would be great! > > Yes it does come up periodically, but the solution is already there - > use User.Temp or the SessionData pull tool that Quinton made for 2.3. > > Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
