On Wed, 21 Dec 2011 16:09:21 +0100, Steven Huwig <[email protected]> wrote:
My opinion is that the term "MVC" is often misapplied to simple separation of presentation from program logic. Moreover, it's an architecture that doesn't actually need to be reflected in the code structure of typical web applications. In a web application, the browser is the view, the web server is the controller, and whatever backend code there is is the model. There's often no need to try to subdivide the backend code into MVC again, because the backend code should be leaving presentation up to the browser.
I think I didn't get the point. Can you elaborate?
Sure, it's good to keep formatting separate from database updates, but that's not the same as trying to shoehorn the whole system into one pattern from Smalltalk that's been extended past its original scope.
I think it's clear that with MVC we're not referring to the way it was done with Smalltalk. MVC is a pattern for a better separation of concerns and the recurring problems still exists.
-- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." [email protected] http://tidalwave.it - http://fabriziogiudici.it -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
