Y
yysun
Unregistered / Unconfirmed
GUEST, unregistred user!
这几天开始做 .NET，看了一些材料和演示，觉得与 J2EE 不同的是.NET 根本不重视 MVC。
下面这段话，摘自 http://www.gotdotnet.com/team/compare/petshopfaq.aspx
基本上代表了 .NET 的观点：
Whydo
esn't the .NET Pet Shop Use a Model View Controller (MVC) Architecture?
Our blueprintdo
es not implement Model-View-Controller (MVC) architecture because we believe the MVC architecture of the J2EE Java Pet Store leads to a non-optimal design for this application. The MVC design pattern separates the data representation from presentation (separating a Model from its View) and separates the application behavior from the data representation (separating a Controller from the Model). For an overview of the MVC design pattern please refer to http://java.sun.com/blueprints/patterns/j2ee_patterns/model_view_controller/index.html.
In general, the MVC architecture is meant to achieve the following benefits:
-Separating data representation from presentation (or separating the Model from the View) allows multiple data presentations for the same data. Changes can occur in both the Model and View components (their interface must remain the same), allowing for maintainability, extensibility, and testability.
-Separating application behavior from the data representation (or separating the Controller from the Model) allows the users requests to be mapped from the Controller to specific application level functions in the Model.
The .NET Pet Shop uses a light-weight componentized design, and achieves essentially the same benefits with much less code required. The result is a more streamlined application that is both easier to create and easier to maintain over time. Also, the performance of this architecture is much improved over the MVC architecture of Java Pet Store according to our tests.
我现在就开始怀疑：Web application 要不要 MVC ？
下面这段话，摘自 http://www.gotdotnet.com/team/compare/petshopfaq.aspx
基本上代表了 .NET 的观点：
Whydo
esn't the .NET Pet Shop Use a Model View Controller (MVC) Architecture?
Our blueprintdo
es not implement Model-View-Controller (MVC) architecture because we believe the MVC architecture of the J2EE Java Pet Store leads to a non-optimal design for this application. The MVC design pattern separates the data representation from presentation (separating a Model from its View) and separates the application behavior from the data representation (separating a Controller from the Model). For an overview of the MVC design pattern please refer to http://java.sun.com/blueprints/patterns/j2ee_patterns/model_view_controller/index.html.
In general, the MVC architecture is meant to achieve the following benefits:
-Separating data representation from presentation (or separating the Model from the View) allows multiple data presentations for the same data. Changes can occur in both the Model and View components (their interface must remain the same), allowing for maintainability, extensibility, and testability.
-Separating application behavior from the data representation (or separating the Controller from the Model) allows the users requests to be mapped from the Controller to specific application level functions in the Model.
The .NET Pet Shop uses a light-weight componentized design, and achieves essentially the same benefits with much less code required. The result is a more streamlined application that is both easier to create and easier to maintain over time. Also, the performance of this architecture is much improved over the MVC architecture of Java Pet Store according to our tests.
我现在就开始怀疑：Web application 要不要 MVC ？
