Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

What is the main difference between Mvc1 and Mvc2 Architecture??

Answer Posted / brainwaves4all

There is nothing called MVC1 and MVC2.

MVC is an architecture for Application development in general. It is not specific to Desktop Applications or Web Applications.

MVC was designed considering the scalability aspect of an application development architecture which implements the clearest possible separation of concerns among its components so as to produce a well de-coupled and highly extensible Application as a result.

The MVC1 and MVC2 confusion comes in due to the Model1 and Model2 designs promoted for the use of JSP and related technologies in Web Application development. So, Model1 and Model2 DO NOT equate to MVC1 and MVC2 respectively for the simple reason that the latter duo do not exist!

Model1 design of JSP puts all logic (both presentation and business kind) in the JSP pages. It has the often dreaded JSP-calling-a-JSP scenario. The scenario is dreaded for the simple fact that most of the business logic is exposed to the world and with raising complexity of the application, the problems of handling the various flows grow enormously. This happens to be the page-centric design which is flawed when it comes to developing scalable applications. Whereas, for simple, small, and use-&-throw applications it is suitable due to its simplicity. The simplicity being one single place for handling most of your logic. This tends to have a lot of redundancy of code when many JSPs perform overlapping functions, though. This makes for another reason why this design is not suitable for large-scale applications.

Model2 design of JSP falls in line with the popular MVC architecture and promotes clear separation of concerns among the components making up the application. The one most important advantage is the resilience of the application to change requests and its ability to scale-up effortlessly. This makes it very suitable for application development of any kind, be it tiny or huge. To this end, JSP pages form the View part, java servlet forms the Controller part, and plain java class files and javaBean classes form the Model part, in this design. The flows follow the MVC architecture's prescriptions.

Please note that there is no mention of the technologies used in MVC architectural implementations in the above response. This is consciously done to drive the point that MVC is an application development architecture that does not concern itself with what technologies implement it in the actual product.

Is This Answer Correct ?    21 Yes 3 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What is the difference between plain-validator and field-validator?

900


Explain about struts dispatch action?

926


Which library is provided by struts for form elements like check boxes, text boxes etc?

868


What is defeult result type?

1014


What kind of mvc is struts 2?

960


What is the purpose of @conversion?

1096


What are the Core classes of Struts Framework?

958


What is actionmapping?

1035


What are the important methods of actionform?

1016


What is the difference between filters and interceptors ?

1034


Why aren’t the struts tags maintained as part of the jakarta taglibs project ?

861


Can I have html form property without associated getter and setter formbean methods?

954


What are the 5 constants of action interface?

962


What is role of action class?

973


What is the purpose of @result?

973