Drawbacks of MVC Increased complexity If reading this page doesn’t convince of you the complexity of this pattern, consider all of the auxiliary patterns that co-occur with MVC. Close coupling of views and controllers to model
Changes to the model interface require parallel changes in the view and may require additional changes to the controller. certain code changes become more difficult. Potential for excessive updates The change propagation mechanism can be inefficient when frequent model changes require many change notifications. This is generally not as much of a problem if a passive model is used. Close coupling between view and controller strict separation is difficult if not impossible. There is a great article on MVC http://www.phpwact.org/pattern/model_view_controller To be honest, in my projects I never faced any troubles using MVC. On Thu, Apr 7, 2011 at 8:25 PM, Rodolphe Gomes <rodolphe.go...@gmail.com>wrote: > Hello, > > I am still having doubts between integrating MVP or PureMVC. > Does anyone has any production experience - drawbacks ? > > Thanks a lot > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-toolkit@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
