Re^4: The Model View Controller pattern in web applications

I agree on most of your points, and I know from experience that MVC can be a huge and costly effort. :-/

I do think that for smaller CGI applications it can still be beneficial to try and separate the three components, because in my experience, those are just the kind of apps that get coded before they're designed.

If you take something like CGI::Application, I think it will make a big difference already for those apps. Even if you don't do the full MVC separation.

Bigger and more complicated applications tend to get more design time anyway (ignoring an abundance of contrary examples), and are _hopefully_ more maintainable just because of that.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re^4: The Model View Controller pattern in web applications

Replies are listed 'Best First'.
Re^5: The Model View Controller pattern in web applications by pg (Canon) on Oct 25, 2004 at 00:07 UTC
Put in this way: From an abstract view: CGI is a totally different animal than MVC, and it is even not a design pattern, but rather a functinal part of a system. From a practical view: I agree that CGI can be used to implement part of the MVC model, especially the V and M. If we are talking about Perl modules, then yes, we can use CGI::Application, even CGI. If you look at what CGI (the perl module) provides you with MVC in your mind, you will quickly realize that: It can be used to form view, with methods like start_form, h1 etc. But I would largely prefer templating systems. It can be used as part of controller, with methods like cookie etc. However if the developer or designer has too much CGI in his mind, then most likely he would come up with something does not clearly sepearte M and V.	[reply]

Replies are listed 'Best First'.

Re^5: The Model View Controller pattern in web applications
by pg (Canon) on Oct 25, 2004 at 00:07 UTC

Put in this way:

From an abstract view: CGI is a totally different animal than MVC, and it is even not a design pattern, but rather a functinal part of a system.
From a practical view: I agree that CGI can be used to implement part of the MVC model, especially the V and M. If we are talking about Perl modules, then yes, we can use CGI::Application, even CGI. If you look at what CGI (the perl module) provides you with MVC in your mind, you will quickly realize that:
- It can be used to form view, with methods like start_form, h1 etc. But I would largely prefer templating systems.
- It can be used as part of controller, with methods like cookie etc.

However if the developer or designer has too much CGI in his mind, then most likely he would come up with something does not clearly sepearte M and V.

[reply]