Controller After Handler

[lightglitch]

I would like to have a way to define an handler similar to "middleware handlers" but that is executed after the controller action is called and before the "$app->after".

The reason why I don't want to use the "$app->after" is that I want to define this handler just for a Controller Provider not for the entire App.

[lightglitch]

I'm going to create a pull request for this what do you think is the best solution:

1 - Replicate the "middleware handlers" behavior with a different name
2 - Add a new parameter to the "middleware handlers" where you define if ti's executed before or after

[igorw]

I have been thinking about moving to a more generic middleware stack à la connect/express. IMO the current architecture cannot hold the added complexity of specific after middlewares. If we want to support this, we need to simplify the architecture so that there is no difference between controllers and middleware handlers.

[webholics]

My personal opinion is that the current naming of middleware handlers is not precisely correct. A middleware should be something which wraps the controller. This means a middleware needs to be able to alter not only the request (as it is now) but to alter also the response. To reduce complexity I would rename "middleware" to "before" and introduce an "after" filter which can be bound to the controller:

$app->get('...', function() { ... })
->before(function(Request $request) { ... })
->after(function(Response $response) { ... });

I think this approach would be much more consistent.

[fabpot]

see #362

[lightglitch]

Looks good to me, that was what I was thinking about.