MVC - where to save the session data?

This guy on our team is working on a form application. Lots of fields in this form. Employee info, address, stuff.

He doesn't have "you're timing out" popup.  As user goes from page to page, he does NOT save the information in database. He saves the fields data user populates in  server session

So, user times out and they don't know they've timed out... user clicks to another page after 20 mins whatever and they've lost their data.

1. My manager says to use the browser session to store the data until user clicks submit
2. Developer says he can extend the session timeout but he says this will affect all users and will take up resources. He says at most..5 people are using this application but has lots of fields for user to populate

3.  He says he can have "you're timing out" popup but even if he does....and user times out... the data is gone, no?

4. We can't have viewstate (my manager mentioned this)....this is MVC

5. I say at each step, when user clicks "Next"... data should be saved in a temp table in the database. User logs back and can pick up where they left off.

What should we do? use browser session? save in DB?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kaufmed 👽Commented:
1. Like just in the page itself? Or in something like local storage (or heaven forbid, a cookie)?

2. Sure it will take up resources. Will it negatively affect users? Are we talking like 50,000 fields per user? It's doubtful that 10 - 20 fields will result in a significant performance issue...unless your server is woefully under spec'd.

3. Well yeah. That's what happens when the session times out. You can prolong this by pinging the session every so often, since session has a sliding timeout.

4. No, and why on earth would you?

5. You certainly could. You can even have session state itself stored in a database. Obviously this is slower since there's a database call. But it can also be scalable if you end up in a load-balanced web server layout.
CamilliaAuthor Commented:
#1 . I think my manager meant in the page itself. If we want to save in a local storage...what are our options?
kaufmed 👽Commented:
Not sure what you mean by "options". Local storage is an HTML 5/Javascript API. There's also "session storage" that's a part of that API. The difference being:  local persists until manually deleted; session persists for life of browser tab.

If memory serves, there is a size limitation of how much you can store in either of those, but it's MB worth of data.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CamilliaAuthor Commented:
let me see
CamilliaAuthor Commented:
thanks, passed on the info.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.