Nice paper on Model View Presenter

Here's a nice paper I found off of reddit this morning explaining the adjustments made to go from MVC to MVP and some historical background.

http://www.object-arts.com/papers/TwistingTheTriad.PDF

About Jeremy Miller

Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in Design Patterns. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • James Gergen

    You MVP Pattern requires the View to have too much business logic. The view should simply implement an interface in which the presenter may interact. The business logic should be contained within the presenter and perhaps a model service.