Re: Session ManagementAgree that hidden variables can be used to store some values, but this may lead to higher network trafic. Yeah for large applications the session scope may become to big to be handled by memory.
So what is the workaround for such an application ? We are currently in process of gathering the requirements of a BIG system. At the same time we are deciding infrastructure related items. What is the best practice in Large systems to handle the Session. Regards Puneet ----- Original Message ----- From: Phil Steitz To: Struts Users Mailing List Sent: Saturday, January 11, 2003 4:45 AM Subject: Re: Session Management Puneet Agarwal wrote: > Session Management is required to achieve persistence. there are two manner > in which persistence can be achieved. > > 1. storing the information in HTTP session (possibly in session scope) > 2. Storing the information using stateful session beans. You can also use hidden fields (basically client-side state management), or application-managed durable storage (e.g RDBMS). > > You have to take the decision based on your application's performance > expectations. > > The cleaner approach is to define the scope of form as "session" and storing > everything in formbeans, nowhere else. > some readonly information can be stored in application context also. > > Well you may choose to store some information in stateful session beans and > some in formbeans (HTTP session) but I would not suggest to keep the scope > of formbeans as "request" unless the screen is totally stateless. Or unless the application has to scale to very large volumes, in which case you want to be very careful about creating too many session-scoped objects. > > Regards > Puneet > > ----- Original Message ----- > From: "JONATHAN PHILIP HOLLOWAY" <[EMAIL PROTECTED]> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Sent: Friday, January 10, 2003 4:10 PM > Subject: Session Management > > > Hi everyone, > > I'm wondering about the ways of managing sessions in Struts and wanted > to know out of these two ways which was the better way of doing things: > > 1. Storing things within the standard servlet session > > 2. Using a UserWrapper object and storing that within the session. > > Is the second way more preformance intensive or not and which is best > practice? > > Many thanks, > Jon Holloway. > > *---------------------------------------------* > Jonathan Holloway, > Dept. Of Computer Science, > Aberystwyth University, > Ceredigion, > West Wales, > SY23 3DV. > > 07968 902140 > http://users.aber.ac.uk/jph8 > *---------------------------------------------* > > > > -- > 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]>
