On 3/20/06, Dakota Jack <[EMAIL PROTECTED]> wrote: > MVC is not a "pattern" and never has been. MVC is composed of various > patterns, e.g. the relation between the view and the controller is normally > based on the Strategy Pattern and the relation between the view and the > model is normally based on the Observer Pattern. There are others. > Further, the web cannot, for obvious reasons implement the classical MVC GUI > archietecture. There is, for that reason, a web-MVC. Again, as Ted has > pointed out, the web-MVC is based on the view --> controller --> model or > controller --> model --> view , depending on whether you are talking about > the request or response. If you couple up the whole shebang with both view > --> controller and view --> model, I am personally not interested because > that is a design mess. >
First, the Strategy Pattern is one STRATEGY to implements the controller, it isn't essential. JSF goes this when it handles event. It looks at the nature and the source of event, and then execute the registered listeners. It isn't different from what Struts does. Struts look at the request which can be seen as an event by the way and handles it to the correct action, which is in reality a request event handler. Once again, a view in JSF knows nothing of the controller, I don't know where you have taken this part. >From what I know, the web MVC exist because the model can't send event to the controller or to the view, hence the Observer pattern can't be used, because of the nature of the Http Protocol. Basically you loose the interactions coming from the model to the controller and the view. > These distinctions bo back before Java itself and are not Struts progeny. I have programmed in Smalltalk and used Swing API in the past so I have don't narrow my point of view to my Struts experience indeed. -- Alexandre Poitras Québec, Canada --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
