php - Controllers and pages without "actions"? MVC -

as understand "mvc" came before web , used in desktop software example.

if understand correctly, controller runs @ time user click button , trigger action.

but if talk web pages, scenario little different, assuming user clicks link triggers action.

but then, came me doubt, home page part of controller?

what mean is, homepage not performed user action within website home, noticed many php frameworks use controller home, correct?

another doubt in "home" have several items, example:

• banners
• featured posts
• recent posts

each of these items have different model, can call more 1 model , view controller?

would these correct steps? or of php frameworks not strict?

you right , understand confusion.

in pure mvc approach, controller listens user actions , updates model accordingly. model notifies view (through observer design pattern) , view updates itself, accessing data needs model. how done before web, in desktop application, model , view running concurrently, , model can notify view. controller doesn't set view.

in pure mvc model, example mentioned homepage doesn't need controller indeed. view render itself, accessing data needs through model. controllers thin , listen user actions , update model. that's do.

in web, model not possible, , there alternative approaches. model can't notify view in pure model, , popular frameworks require do, set view in controller. that's why example of homepage need controller, set view there data requires.

however, there approach have been writing about, controllers don't set view allow keep tiny controllers. can read here: a better oop approach building mvc applications

thus believe homepage shouldn't need controller action @ all. view should render , access data needs render. controller's role handle user actions , update model accordingly, said. if more that, violates srp. controller shouldn't set view, instead, the view should own data model.