I'm working with an MVC framework to build a simple Q&A web app, and I am trying to grasp the idea of controllers acting on the app.
For instance, say I have a home page with the following links:
- Home > Login > Home > Profile
- Home > List of questions (updated dynamically) > (new view showing) One question
- Home > List of top answerers (updated dynamically)
In this case, would it make sense to have two controllers, namely - QuestionsController: to bring recent questions from Question model - UsersController: to help login and bring top-answerers from User model
I did some research and found out that I could use a SessionsController for the login/logout. Of course, the main ApplicationController is there too. Then for this view alone, there seem to be 4 controllers working... Is this decent practice?