This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
As you mentioned in the above answer that in MVC we can modify the server side methods without affecting client side code. that means we Cant do this in 3 tier...???
other this is you said we can use MVC irrespective of tier? i was under impression that in 3-tier also we can use irrespective of tier..??
Joined: Aug 03, 2003
You can use MVC in 3-Tier/n-Tier. More precisly MVC is used for best approach to integrate Server side and Client side code, where 3-Tier/n-Tier is used to reduce the load of the servers. If your app server has high load, add some more servers to reduce the load. For http related requests use webserver. As the number of servers increases, tire will be increased. Do not compare MVC and n-Tier, both are different.
is it clear for u?
Joined: Nov 29, 2004
Yeah i got that, 3tier/n tier is not for integration of server side and client side things, this is just to reduce the load on server ..right??? then what is the difference between MVC -1 and MVC-2 ??? as both (MVC -1 and MVC-2) are used for the same purpose... is MVC-2 related to 3 tier/ n tier??
Here is my take on this. Let's say that a well-designed system has three layers: presentation, business logic and data storage. For an MVC architecture, the model is in the business logic layer, and the view and controller are in the presentation layer. MVC does not really address the data storage layer.
So, the layers may have the following (let's say that Struts is used as the MVC implementation).
Presentation ============ HTML CSS JSPs Servlets Struts files and classes
Business Logic ============== Business objects EJBs
Another distinction to keep in mind when trolling through books or magazine articles, is that there is a difference between MVC as it is used for desktop GUI applications versus the web variant of MVC. Originally MVC came from the Smalltalk world and was really an extrapolation of the observer pattern. The idea was that changes to the model would cause propagation notifications to be delivered to the view, which was an observer of the model. You can't really do that on the web unless you are using something like Ajax or an Applet, so the view and controller interact a lot more on deciding when to pull data from the model to update the view. [ January 20, 2006: Message edited by: Reid M. Pinchback ]