Re: Re: MVC and PHP

I agree with Justin, and is very common to forward to a page based on the model response to a request, like a simple login sistem. Especially for web, MVC should be called MAVC ( Model, Action, View and Controller), where action is called by the controller to exec all the code for a View. The Action instantiate all the models necessary to fill the view. At 12:35 3/2/2004 -0800, Justin Patrin wrote:

SâòÏio Carvalho wrote:

Citando Joe Stump <joe@joestump.net>:

Stable, proven and working. Yet completely useless under IIS or any of the other webservers PHP/PEAR runs under. PEAR is about standards, interoperability and compatibility - not catering to just Apache.

On IIS, I have good experience using ISAPI_Rewrite Lite Version, which is free. Even the full version is a fraction of the IIS license cost: http://www.isapirewrite.com/ My point is that MVC patterns -- extremely useful in GUI apps -- translate only to URL rewriting under Web applications. URL Rewriting is much better done by the web server, before handing out the request for module processing.

I don't agree at all. Using the basics of the MVC framework (seperating Model, View, and Controller) is extremely useful in web applications as well. JUst like any other design pattern, it's not useful for every single program, but it's highly useful for most somewhat complex web apps. Simply seperating the View from the rest is particularly useful in web apps. Especially if you use a template engine like Smarty or Flexy. It allows easy editing of the look of the program without having to wade through and understand mounds of data and logic code. The same goes for seperating the Model and Controller. Seperating the data into its own classes allows for easy changing of data-specific functionality without messing with the program or display logic. -- paperCrane <Justin Patrin> -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php