This is an archived low-energy page for bots and other anonmyous visitors.
Please sign up if you are a human and want to interact.
in reply to Implementing Model-View-Controller
You may be getting confused by the fact that most of the current MVC web tools (CGI::Application, OpenInteract, Catalyst) are fairly different from the approach described in the classic MVC theory articles. These days, MVC for the web usually means one class that handles all the web interaction (the controller), some fairly basic classes for updating a database with Class::DBI or similar (the model), and some templates (the view). It's not exactly MVC, but it's a simple approach that works well. If you look at some of the many sample apps written with any of the three tools I mentioned, you'll see this basic approach. |
Re^2: Implementing Model-View-Controller
by ruoso (Curate) on Jan 05, 2006 at 08:52 UTC
|
| [reply] |
|
|
I would say that the differences in the view are less significant than the way the model has been changed. Putting application logic in the controller was not part of the original idea, but since everyone now uses basic O/R mapping tools like Class::DBI as their model, all the logic that used to go in the model ends up in the controller.
| [reply] |
|
