Session is probably the way to go. For things like this, i.e., data that is transient on the whole but needs to persists across a number of requests, session is probably the right choice.

Why WOULDN'T it be the right choice? If your storing a lot of data, session can become a problem, especially if you might deploy to a distributed environment. Second, if you expect a very large number of requests, you may find server resources being chewed up more than you'd like and performance might ultimately suffer. Also, if you need the capability of saving the steps of the wizard for later, you'll need a more permanent persistence mechanism. These are just some of the concerns.

All that being said, from what you describe, I'm thinking session without hesitation. Not much data, your entire process takes a couple of steps then some final result (which may be more permanently persisted, I don't know)... Session coding will be very easy, and unless your going to have a huge load, there shouldn't be any problem. Only you know all the details though, so you'll have to make the real determination.

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com

Koon Yue Lam wrote:
oh, so I need some way to store data in the respond object
I know session can be help, is it a right way to do?
It is not very big object but it would be an array of String (which
contains user's multiple selection)

thanks for your help, ^^

---------------------------------------------------------------------
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]



Reply via email to