Due to these answers, I've decided to implement MVC (or a variation of it) into my application. But the more I read the more confused about this topic I get. Some people say the business logic belongs to the model, some say the model should only holds data/a state, some say the logic should be entirely in the controller class(es), and for others the controllers are just the glue between the model and the view to display the information the model holds.
In my specific application, the process I want to put into an MVC pattern can generally be divided into these parts:
- Retrieve information from the web server
- Interpret/Parse that information and store it in variables
- Take those variables and display them.
I can seperate these processes, but they are not exactly what an MVC pattern should look like. I'm not even sure if I can apply the MVC pattern here. There is no real persistent data in the application, only the variables where the parsed things are stored. MVC mentions nothing of retrieving or interpreting the data. Have I overlooked something or do I just need a different pattern here?