I applaud this user for sticking his neck out to write such an article, but I find it quite lacking. "MVC is designed to solve the problem of simultaneously h

I applaud this user for sticking his neck out to write such an article, but I find it quite lacking. "MVC is designed to solve the problem of simultaneously having multiple control entry points, and multiple display outputs, and it acheives that very elegantly. But web applications only ever have one entry point and one output point - the request and the response. You don't have multiple simultaneous controls or views to worry about, so there's little point applying traditional MVC to solve this non-existant problem. Your application, be it a CGI script, mod_perl handler, or even an all-in-one embedded Perl template, receives one and only one request for any one invocation, and it must generate one and only one response. Flow of control is linear and predicatable." Any web application that can be reached at from a web-enabled phone, a desktop, has API calls to respond to, feeds to deliver and 3rd-party apps to integrate with can hardly be classified as having one entry point and one exit point.