MVC Template - The Right Way to Think About It

Read dozens of articles about MVC, and right now, this is one mess for me. I am trying to do the right thing with my project, which I am rewriting from procedural php to oop, however, I am confused.

I am sure the model should include all the business logic that makes sense imo. Not too sure about the view. Should I transfer the data to the "View" and display the template accordingly, or should the View simply request the data it needs (from the updated model)?

Read a lot about this on SO too, but it just got worse. The answers are different, and I lost a little.

What is the correct explanation of the MVC pattern? (Well, I know that it may be different here, but the point must remain)

MVC 1

enter image description here

MVC 2

enter image description here

+4
2

- ASP.NET MVC , ! ( , ).

, , url , , , , , .

, !

+1

,... ** . , , , :

  • stuf

, , , mysql, , , .. , , . html, css .. php , , ifs.

.

0

All Articles