[Import] Web client software factory series (3): View-presenter mode

Abstract: an ASP. NET site is separated into multiple independent modules. The biggest problem is that most of the business logic associated with the page resides on the page. Source codeFile, we almost cannot CodeFiles are divided into multiple independent ProgramSet. To create an independent function module that is associated with pages on the site, all page logic, event processing logic, and navigation logic must be extracted from the page in some way and stored in an independent set of programs.

The default solution in the Web Composite Application Block is to use the view-presenter mode to divide the page logic into different classes (proxies) used to respond to any event forwarded by the view (web page ). The representations class is fully implemented in the business module, so that the application logic is out of the website. interfaces are defined in the business module that defines the methods implemented by the view. In this way, the web page can forward all events to the dashboard at the end, without any actual responsibilities specific to the application. This also makes it easier to test the design dashboard without actually involving the front-end web page. Read the full text

Terrylee comments

ArticleSource: http://www.cnblogs.com/Terrylee/archive/2007/11/27/Web-Client-Software-factory-view-presenter.html