title: In MVC, what is a ViewModel?
body: <p>Am I right in thinking it's almost like a wrapper for all the objects necessary for a View?</p>
  
  <p>For example, say you had an online store that sold music and dvds. On your browse page you'd want to display a list of all your dvds and music. Would you therefore construct a ViewModel object that has two properties containing an albums list and a dvds list?</p>
  
  <p>From my understanding it seems that you have all your model classes ie. an Album/Dvd class, but simply passing these alone wouldn't be enough for your View. Does a ViewModel basically act as a carrier for all the data your View requires?</p>