[NFR] Implement afterInitialize event in dispatching loop

[iforp]

This issue is a continuation of this #703

For now events priority looks like this:

• SomeListener::beforeExecuteRoute
• Controller::beforeExecuteRoute
• Controller::initialize
• Controller::afterExecuteRoute

With ACL check now it's perfect: beforeExecuteRoute performs ACL check, so controller will not be initialized if user not authenticated.

In some cases we need to perform some operations after controller was initialized but before executing action.

My current case is parse CLI options to set controller params.

Of course I can call like this

    public function initialize()
    {
        // register all I need
        // ...

        $eventsManager->fire("dispatch:afterInitialize", $this, $extraData);
    }

but core implementation would be more usable

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[ghost]

@Agent-J could you please check if this works for you?

[Green-Cat]

@andresgutierrez Implemented in #984. Also present in 2.0

cphalcon/phalcon/dispatcher.zep

Line 496 in 3070344

if eventsManager->fire("dispatch:afterInitialize", this) === false {