"Transformation of data" makes a lot of sense if you're accustomed to "pipes and filters" architectures. It's anything your program might actually do with data that passes through it. Doesn't matter what it is – it's a black box!
Why should handlers and actions be separated? Because they're different things! This is already standard in web architectures: the router is a collection of handlers and the functions that the router calls out to are actions. I like that actions are separated out from the monolithic "controller".
Comments
Ah, RAPHT is so much clearer than MVC: https://github.com/DanielWaterworth/Raphters/blob/master/RAP.... I would love to see more projects adopt this architecture.
Is it? It's not really clear what a 'transformation of data' entails, or why handlers and actions are separated.
"Transformation of data" makes a lot of sense if you're accustomed to "pipes and filters" architectures. It's anything your program might actually do with data that passes through it. Doesn't matter what it is – it's a black box!
Why should handlers and actions be separated? Because they're different things! This is already standard in web architectures: the router is a collection of handlers and the functions that the router calls out to are actions. I like that actions are separated out from the monolithic "controller".