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. All this ends up looking something like:
- The server side View tries to manage and encompass everything that happens in the browser – including JS – and the code still looks like spaghetti
What’s needed is to rethink web application architecture. What’s needed is a new MVC pattern- er, patterns.