This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi, guys. Well I've been in a discussion recently about MVC: - I believe MVC architecture composes the presentation tier, correct? - People are telling me MVC is composed of 3 tiers: Model - View - Controller. I think that's wrong. MVC is a whole architecture for the presentation layer.(Correct me if I'm wrong). I believe Model - View - Controller are just patterns that compose the whole architecture, not a layer itself. - And therefore, MVC is just one tier. What can you say about this? Thanks in advance.
Jean Rodrigues<br />SCJP / SCWCD / SCBCD / SCEA I / SCJD (Finishing)
Model, View, and Controller are concepts which you can use to explain a software architecture. In the classic Smalltalk implementation, each concept is an object. In Swing, for eaxh widget the View and Controller are smooshed together into one clump of objects, and the Model is another object. But it's not incorrect for me to talk about a classic 3-tiered architecture seeing the database as the Model, the middle tier as the Controller, and the GUI as the View. Now, in this case, the View is actually a complex thing which itself contains a separate Controller and View, and uses the lower tiers as a Model. But as I said, these things are just explanatory concepts, and you use them whenever they make sense.