@samsonasik 👍 , but you should probably also replace usages...

@Ocramius I replaced usages of 'ControlleLoader' to 'ControllerManager' at library and tests folder, now it is safe to remove 'ControllerLoader' from ModuleManagerFactory because of already aliased. Let me know if something missing ;)

@weierophinney done ;)

I'm still worried about BC implications of this.

If a developer has created a factory for ControllerLoader, the assumption is fetching the ControllerManager service will fetch that instance -- but with this change, it would not. I'm thinking we may need to bench this one until 3.0.

@samsonasik Can you post an email to the zf-contributors mailing list, pointing them to this PR and:

• summarize what you are doing
• explain the BC concerns
• ask for feedback

Thanks!

@weierophinney i have posted here at mailing list here : http://zend-framework-community.634137.n4.nabble.com/Need-PR-review-for-4962-added-quot-ControllerManager-quot-Manager-and-make-quot-ControllerLoader-quo-td4660773.html . Let me know if something missing, Thanks.

For ZF3 I'm in favour of renaming all this mess to "ControllerPluginManager", "FilterPluginManager"... and so on =). But even, this is somewhere we're not consistent. I love using FQCN for keys, and we use it sometimes even inside the framework ('Zend\Authentication\AuthenticationService' for instance).

We need to have a consensus on that =).

@bakura10 this PR can be a preparation for ZF3, I make an alias of ControllerManager pointed to ControlletLoader to make it's still compatible with current version 2. When ZF3 released, the "ControllerLoader" manager that deprecated can be completely removed.

I'm not sure how only changing the name will benefit ZF3, when ideally its functionality should also change in order to make it an independent factory, below is along the lines of what I would like/expect to see in ZF3:

public function createService(ServiceLocatorInterface $serviceLocator)
{
    $config = $serviceLocator->get('Config');

    $controllerConfig = new ControllerManagerConfig($config['controllers']);

    $controllerManager = new ControllerManager();
    $controllerManager->setServiceLocator($serviceLocator);
    $controllerManager->addPeeringServiceManager($serviceLocator);

    $controllerConfig->configureServiceManager($controllerManager);

    if (isset($config['di']) && isset($config['di']['allowed_controllers']) && $serviceLocator->has('Di')) {
        $controllerManager->addAbstractFactory($serviceLocator->get('DiStrictAbstractServiceFactory'));
    }

    return $controllerManager;
}

@devosc : +100. I'm advocating using the SM config to create all plugin managers (that's what I'm doing in my ZF3 hydrator refactoring too). This will allow us to remove the infamous ModuleListener class. However we need to have a discussion about this with the team as we loose a feature (the ability to specify config in a Module.php class using the getControllerConfig method - I think it's not a big deal as people can still use the global getServiceConfig).

Changing names is just a coherency. ControllerLoader was confusing because most other plugin manager ends up with manager. At the same time we also have some plugin managers that ends with PluginManager (which is the suffix I prefer). It's all those small things that make the framework easier and more coherent to use, even if this is not a feature change.

@devosc This PR is for preparation for ZF3 for more consistency, just to start consistency with naming. I think the changing code can be applied when starting ZF3

The thread started via Nabble didn't come to my inbox, so I'll leave my comment here.

Personally, I'd rather see a ControllerManager alias added now rather than changing the class names and everything and aliasing the old to the new. Aliasing the future names to the existing names gives less risk of a BC break in 2.x. I agree with 3.x we should move toward more consistent naming, etc.

@EvanDotPro can you clarify the specific changes you feel should be made for this PR to be ready to merge?

ping @EvanDotPro ^^

@samsonasik what @EvanDotPro is indicating is:

• Keep the original factories/services
• Alias the future names (e.g., ControllerManager) to the present names (i.e. ControllerLoader) (I think this may be the current situation).

The rationale is it ensures BC is kept in 2.x. In 3.0, we would change the situation, and make the new name the actual service, and potentially have a "compatibility layer" that would alias the old service names to the new.

@weierophinney done ;), I keep the original factories, and added alias ( ControlerManager ) for it. Please let me know if I missed something. Thank you.

I updated code to reference the "ControllerManager" service, including tests, and noted the change in the README. Merged to develop for release with 2.3.0.

re-created in zendframework/zend-mvc#6