I recently added a new feature branch for 2.2, with the ability to add listeners to the dispatching process. Those would act as some sort of middleware that could be used for tasks varying from caching to authenticating a user. Additionally I extracted the asset and cache dispatching into filters, so they can be swapped or disabled at will.
The only thing I'm no completely sure is whether we should trigger the afterDispatch event when calling requestAction (beforeDispatch event is correctly being triggered right now). Do you think we should trigger it? I think the use cases are inexistent, given that this callback wil only be able to alter the response headers and perhaps the body, wich are not actually valid use cases for requestAction imo.
Thoughts?