> -----Message d'origine----- > De : Ramprasad A Padmanabhan [mailto:[EMAIL PROTECTED] > Envoyé : mardi 14 juin 2005 16:39 > À : beginners@perl.org > Objet : what is the MVC all about > > > hi, > I have been lately reading a lot of stuff about perl > catalyst with MVC I am still not clear about practical use of > MVC's Can someone provide pointers about MVC and where they > are best used ? >
I liked a lot thoughts on MVC from Andy Wardly (Template Toolkit Author, tt2.org): "I suggest that a clear separation of concerns is what is really important, and while MVC is one way of achieving it, it is not the only way. By concentrating too closely on an MVC architecture, it is possible to overlook other important aspects of the system that warrant clear separation." "What the MVC-for-the-web crowd are really trying to achieve is a clear separation of concerns. Put your database code in one place, your application code in another, your presentation code in a third place. That way, you can chop and change different elements at will, hopefully without affecting the other parts (depending on how well your concerns are separated, of course). This is common sense and good practice. MVC achieves this separation of concerns as a by-product of clearly separating inputs (controls) and outputs (views). So in my opinion, it is the separation of concerns that is important rather than the MVC design pattern in particular." Quoted from http://wardley.org/computers/web/mvc.html HTH, José. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
