RE: Should controllers be "smart"?


Sorry for the confusion. The others are absolutely right. I have
translated the traditional 3-tired architecture (data layer, business
layer, presentation layer) right into the MVC pattern. This is
completely incorrect.

Prior to ORM tools and the like, I would typically create my classes to
be data (direct calls to from database), business (handles all business
specific functions and calls the data object), and presentation jsp/php,
etc. I somehow associated that as being the same as MVC.



This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs