Typically the best solution is to keep this data in the session. That is what the session is for. As I mentioned, the other option would be to encode the data using base64 encoding (or something similar) and store it in a single hidden field.
What makes you so sure you have "too much" data in the session? Perhaps you could streamline some of the other data you store in the session or make sure you cleanup unneeded data. -Adam -----Original Message----- From: Emilia Ipate [mailto:[EMAIL PROTECTED] Sent: Friday, June 09, 2006 8:04 AM To: Struts Users Mailing List Subject: RE: best way to send parameters through more requests Using hidden fields is good, but what if you have like 4-5 request steps? You will end up at step 5 to send to server a long list of hidden fileds (all the fields used in step 1,2,3 and 4)... And this sounds like a unmaintable code!!! Emilia -----Original Message----- From: Samere, Adam J [mailto:[EMAIL PROTECTED] Sent: vrijdag 9 juni 2006 13:57 To: Struts Users Mailing List Subject: RE: best way to send parameters through more requests You also may be able to store state in hidden fields in the rendered markup, or by encoding the raw binary data in a single hidden field. This goes a bit beyond the scope of this list though. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 09, 2006 7:40 AM To: user@struts.apache.org; [EMAIL PROTECTED] Subject: RE: best way to send parameters through more requests Also a word of caution I presume all the objects you store in session are seriallizable. If they are not then your solution wont work if the application is deployed on cluster Small piece of information can be transferred through hidden fields from form to form through struts actions Cheers -----Original Message----- From: Dave Newton [mailto:[EMAIL PROTECTED] Sent: 09 June 2006 12:33 To: Struts Users Mailing List Subject: Re: best way to send parameters through more requests Emilia Ipate wrote: > Is there a solution besides using session, to send some request > parameters from one request to another? > I would like to implement something like a shopping cart (a > functionality which needs about4-5 steps) and I do not want to store > the objects in the session (it is alread too big)! > > So, do you have any ideas? Keep the shopping cart in the DB and load it on every page. Personally I'd rather keep things like that in the session, though, unless there's a requirement to keep the cart sticky. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ----------------------------------------- The information contained in this message may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or any employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Paychex, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
