Home/ Questions/Q 6319217
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T15:46:04+00:00

In my world, the model notifies only the controllers subscribed to the model’s event.

  • 0

In my world, the model notifies only the controllers subscribed to the model’s event. Then the controller tells the view what to do, for example adding a new row to a list.

The same with the view: the view notifies the controller subscribed to the view’s event. Then the controller modifies the model as needed, for example setting the name of a person, and call the Save() method on the model.

Okay, I know I’m wrong, I don’t think every article about MVC is wrong because I’m thinking in another way. The point in MVC is to seperate the UI from the data model. How does this come true when the view and the model reach each other? Why should they do so?

Thanks for Your answer!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Model-View-Controller is seen different ways by many people, but I like to think of it as a combination of several other patterns rather than as a single pattern. This may come originally from this note

    The connection of the view to the model is an Observer Pattern, with the model notifying the view when it has changed. There’s no need for the controller to be involved in this.

    • 0