The document-view mode is used in MIS Design. I really don't know much about it.ProgramThe business logic and performance should be separated, but when looking at the presentation layer mode, we found that it is really not a good way to set MVC, but it is consistent with the document-view in the original MFC. After reading Microsoft's msdn model seriesArticleIt is known that document-view is a variant of MVC.
When the system was small, it used to write business logic directly in form. Another reason for this was that the demand was too large, too many changes were made, and the requirement was fast. If you write too much, you will feel that the business logic is scattered in various forms. Once the business logic cannot be reused or duplicated in the system.CodeMany, it is difficult to modify a single error. Second, the business logic is too scattered, and it is difficult to organize the entire business. If the next similar project cannot benefit from the original system. In the beginning, the data access layer was isolated, but the universal data access function, that is, obtaining dataset from SQL or updating dataset Based on select, was provided independently, reading/writing blob and retrieving sequences are not data gataway.
After document-view is used, the main purpose is to clarify the business logic, and the Business modification and interface modification are independent of each other. It is also easy to switch to a three-tier structure, or B/S.