3 ms·
It splits controllers into operations and events. Out of the three terminologies (state, representation, flow), the third one is arguably the most tangled. I f
by pestaa 14y ago
It splits controllers into operations and events.
Out of the three terminologies (state, representation, flow), the third one is arguably the most tangled. I find it healthy to refactor it into reusable chunks (operations) and event-driven flow management.
The problem was, in my opinion, that operations should have not been put into controller units. It attracted more copy-paste solutions in my experience.
- utilitron 14y agoWhat is the difference between that and adding a service layer to a MVC?
- rcgs 14y agoThere isn't, but then is MVC really MVC when you've added in another layer?
- cbsmith 14y ago> It splits controllers into operations and events. The original MVC designs and sample code all had views and controllers observing models through an Observer based event pattern. The operations were the controller units. The events were not.