title: Sessions in ASP MVC
body: <p>I learned that Sessions are no longer the recommended way to preserve data in ASP MVC and rather we should move to ViewData (from controller to View) and TempData ( for one postback only). The only reason why we shouldn't use Session is to maintain the Testability (MVC supports TDD, thus HTTPContext.Session wouldn't resolve while running TestMethods).</p>
  
  <p>But the purpose solved widely by Sessions are still not solved by ViewData or TempData. Session saves the context for throughout the user Session. </p>
  
  <p>I am still not able to collect the correct recommendations and Alternatives for Sessions in MVC. Might be I am mistaken in understanding the correct picture. I would appreciate any links to the discussions or any suggestions from you guys.</p>
  
  <p>This will help me to decide, using Session for the purpose it has been used with WebForms or we should go for rearchitecting the current application so that we can go with Session only where mandatory.</p>
  
  <p>Thanks 
  Sumeet </p>