title: in MVC, where do you draw the line between a controller and model?
body: <p>I've seen code written where almost all non-route related code is passed to a model. I have also seen code where all database persistence is handled by a model, but non-DB processing is handled by the controller.</p>
  
  <p>Which is the better approach?</p>