Let's say I have a web application implemented as a set of wizard pages for editing a complex object. Until the user clicks the Finish button, the object will not be saved in the internal system (requirement), so at the same time I have to store all the information about the object in some session state.
In addition, some wizard pages should display combo boxes and lists with a potentially large number of items. These items are retrieved from the internal system using a web service.
By the way, the wizard allows the user to freely switch from one page of the wizard to any other (using the links on the tab on top of the form), so this is not a simple thing "next, next ... end".
Additional limitation: the web application runs in the web farm, and the client is tired of using the session state on the server side. At best, they want the session size to be minimal (they had problems with this in the past).
So basically there are two problems:
- How / where to store data entered by the user in the wizard?
- Should the combo / list items received from the internal block be cached, and if so, where?
The options I'm considering are:
. ?