There are several flavors of MVC.

In the original concept published 1979, the view queries the model and the model doesn’t know about the views. However constant polling is not so efficient.

Subsequent MVC designs therefore generally see the view as an observer of the model. This means that views subscribe to the model and get notified of changes. The model does not know that it’s a view and can not use the full view’s interface. You’ll find an in-depth analysis of the MVC relationships in GoF.

There are several flavors of MVC.

In the original concept published 1979, the view queries the model and the model doesn’t know about the views. However constant polling is not so efficient.

Subsequent MVC designs therefore generally see the view as an observer of the model. This means that views subscribe to the model and get notified of changes. The model does not know that it’s a view and can not use the full view’s interface. You’ll find an in-depth analysis of the MVC relationships in GoF (page 4 to 6).

There are several flavors of MVC.

In the original concept published 1979, the view queries the model and the model doesn’t know about the views. However constant polling is not so efficient.

Subsequent MVC designs therefore generally see the view as an observer of the model. This means that views subscribe to the model and get notified of changes. The model does not know that it’s a view and can not use the full view’s interface. You’ll find an in-depth analysis of the MVC relationships in GoF.

There are several flavors of MVC.

In the original concept published 1979, the view queries the model and the model doesn’t know about the views. However constant polling is not so efficient.

Subsequent MVC designs therefore generally see the view as an observer of the model. This means that views subscribe to the model and get notified of changes. The model does not know that it’s a view and can not use the full view’s interface. You’ll find an in-depth analysis of the MVC relationships in GoF.