title: DAO pattern and model objects
body: <p>I have looked up a lot of information about the DAO pattern and I get the point of it. But I feel like most explainations aren't telling the whole story and by that I mean where would you actually use your DAO. So for example if I have a User class and a corresponding UserDAO that is able to save and restore users for me, which is the correct way:</p>
  
  <ul>
  <li><p>The controller creates the User object and passes it to the UserDAO to save it to the database</p></li>
  <li><p>The controller creates the User object and in its constructor the user object makes a call to the userDAO in order to save itself into the database</p></li>
  <li><p>This is a code smell and you are missing an extra class "UserManager" which the controller will ask to create the user. The UserManager is responsible for creating the user and asking the UserDAO to save it </p></li>
  </ul>
  
  <p>I really feel like the third option is the best, because all that the controller is responsible for is delegating the request to the correct model object.
  What is your favorite way? Am I missing something here ?</p>