MVP and model

First, it is already clear to me that the most important point of MVC is the separation of responsibilities. Lately I have been reading some articles/Q&A in the web to understand the differences between most popular MVC implementations. Examples: Architecture more suitable for web apps than MVC? http://joel.inpointform.net/software-development/mvvm-vs-mvp-vs-mvc-the-differences-explained/

If I got it right, people say that the major difference between MVC and MVP is that there is no communication between model and view layers in MVP, controller works as a mediator between both. However, I do not see this restriction in MVP original paper: http://www.wildcrest.com/Potel/Portfolio/mvp.pdf, it just seems to add details to the MVC model, in the form of selections, commands and an interactor.

It seems to me that MVP is just an overloaded MVC acronym which may mean one of two MVC patterns: passive view or supervising controller.

Could someone clarify this?

链接地址: http://www.djcxy.com/p/30232.html

上一篇: 演示模型与MVP（被动视图）

下一篇: MVP和模型