Search Google for “web application MVC patterns” or any variant thereof, and the vast majority of results will talk about the server side MVC. This traditional answer will tell you the browser sits outside the MVC altogether, and sends in HTTP requests that are handled by the Controller, then all the MVC garble happens, and finally the View spits out a brand new HTML page (or XML/JSON for AJAX) for the browser to consume.
“So what’s the problem with this model?” you ask? The JavaScript layer of course . All of the code that runs in the browser doesn’t fit anywhere inside the classic MVC architecture.
Link Posted by Tim at August 9, 2008 04:23 PM | TrackBack