and so my research into the world of MCV continues, and suddenly I feel cheated when I discover that the MVC world moved on years ago to something brighter, shinier and newer? MVP - Model-View-Presenter
So for us poor folks lagging behind, do any of the MVC pundits have any comments on Model-Vew-Presenter? My uninformed reading leads me to the following intermediate conclusions: The best explanation [and it covers MVC] that I have found seems to be ftp://www6.software.ibm.com/software/developer/library/mvp.pdf It appears to me that the MVC we are discussing in mod_perl is a simplification of the original - an almost stateless remote user interface is somewhat different from the richly interactive GUI apps that MVC was originally designed for. I would guess that there is no need for Views to register as observers with the Models [is there??] etc. Interestingly, most of the limitations of MVC that led to MVP seem to have to do with the interaction of Controller and View, which led to additional intermediate components that IBM call Interactors. Additional formalisations include the addition of Command components with do, undo and redo methods to communicate between the Controller aka Presenter and the Model, and Selection components to identify ranges and selections of data in the Model to be acted upon. All in all, the additions that led to MVP do not seem particularly applicable to web development - it seems to me that a simplified MVC may work better here. Do others concur? Does anyone know of an MVC disseratation similar to the IBM MVP document, that particularly discussed MVC in a web development context?
