Change of structure of calls to controllers

[xeoncross]

Change of structure of calls to controllers

[xeoncross]

Yes, you are correct. This new implementation of a route loading a single class with an action() method is even more defined in the current development branch which will be released soon.

The reason is simple. The primary goal of MicroMVC is speed and ease.

Each controller action is unrelated to each other, therefore there is no reason for PHP to waste time loading a whole list of controller actions when it only needs one. This also helps to keep files small and organized making it simple to focus on the code you need.

For example, when working on a user class you might have login, logout, edit, register, profile, recent_activity, admin, ban, and other actions. You can either cram them all into a massive controller file (which means lots of scrolling up and down if you are working on it), or you can create a single class for each action.