I decided to use ASP.NET MVC to develop multi-page (registration) forms in asp.net. There will be two buttons on each page, allowing the user to go to the previous and next page. When a user navigates to a page they recently filled in, data should be displayed on them. I understand that ASP.NET MVC should remain stateless, but how do I maintain page information when a user moves back and forth.
Should I?
- Save information in the database and get information for each page change?
- save session information?
- Download all the fields and show just what you need with javascript?
This registration form will be used on several sites, but with different sets of questions (some of them may be the same). IF efficiency is a major issue, should I dynamically generate these forms?
Jay
source
share