title: Where should business logic be placed in a controller/model/view project
body: <p>I am wondering what the best practice is for creating a complex view and model.  </p>
  
  <p>I have been reading that you are suppose to handle business logic in the model, and only use the controllers for handling the request and view results <code>json</code>, <code>string</code>, etc. Is this correct? </p>
  
  <p>I came across another article that said business logic is suppose to be in the controller, and domain logic is in the model. </p>
  
  <p>Also, is it best practice to use constructors, or can this cause issues like having to extend the binder for it. </p>
  
  <p>Any advice, and a reference to a complex design implementation of a model view and controller would be appreciated. </p>