Jump to content

Recommended Posts

Hi all!

 

More stupid questions about MVC, that I haven't had a clear answer and just have to make my self clear.

 

Right now, I am in a mindset, that the controller asks model for some information, puts it into a variable, and sends it to a views variable. This seems fine to me, but now i am having second thoughts.

 

Should it be more, like that I STORE the data at the model as well? Like if I get the site navigation from the DB, and define what page I am currently on, should I store that information in the MODEL and have a method to call it from there, even from the view, or should I store the the info in controller's variable, and just send it to the view?

 

Thanks alot in advance!

 

-NikkiLoveGod

Link to comment
https://forums.phpfreaks.com/topic/132502-clearing-up-mvc-each-parts-correlation/
Share on other sites

controller asks model for some information, puts it into a variable, and sends it to a views variable

 

Controller chooses view and view interacts with model. But controller has responsibility for updating model (adding data from form etc.)

 

Here is nice summary: http://www.phpwact.org/pattern/model_view_controller

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.