title: MVC - Persisting viewmodel data between requests
body: <p>I am looking for some suggestions or possibly a solution I've overlooked for an issue I have with a project I am working on.  It involves persisting ViewModel data between several requests.  Here's an example:</p>
  
  <p>User is on a specific page that contains a few form fields and a grid of items related to the underlying model.  The user needs to add an item or items to the grid, so I have to redirect them to another page to select some of these items.  After the user has selected their items on this page, I need to send them back to the original page with the items displayed in the grid.</p>
  
  <p>I have this working, but what I'm doing is before they are redirected to the second page, I am storing the ViewModel for the original page in session, updating the ViewModel appropriately with the selected items on the second page, then redirecting back to the original page and using the ViewModel from session to populate the form fields and grid.</p>
  
  <p>However, I don't think this is the best solution and scalability is going to be an issue since this project needs to be scalable, and throwing stuff around in session is not a desired solution.  I've read the multitude of suggested similar questions but I've found nothing that really pertains to my specific situation.</p>
  
  <p>Has anyone ever done anything like this and has found more reliable solutions, or possibly has some suggestions on a different implementation.  Thanks.</p>