On Apr 1, 2005 11:31 AM, Joe Germuska <[EMAIL PROTECTED]> wrote:
> You have a point, Frank, but more importantly, people have to
> remember that the original MVC pattern applied to an event driven
> unified runtime environment, not a request/response environment.
Back when we were writing Struts In Action, I did correspond with the
originator of MVC, Trygve Reenskaug. He told me that, in his opinion,
the Observer pattern is not required by MVC. It was simply an
implementation detail. What's essential is that the View is able to
render itself from a representation of the Model, as we do with the
JavaBeans strategy.
Subscribing to an object that is watching the database for state
changes, and then apprising subscribers when a change occurs, is one
way to implement MVC. Posting a the "Model" to the servlet context as
a set of JavaBeans is another.
The key points are that the View is a passive client of the
application state, and that the state representation ("model") is
generic. The View is not running out and querying the database
directly, and the data provided by the model could by different views.
(Could be a web page, could be a PDF, could be a pie chart, could be
a bar chart.)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
