Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

ListenerAggregatePluginManager? #59

Open
abacaphiliac opened this issue Aug 17, 2017 · 3 comments
Open

ListenerAggregatePluginManager? #59

abacaphiliac opened this issue Aug 17, 2017 · 3 comments

Comments

@abacaphiliac
Copy link

hi Team,

assuming that an application has factories for its listeners, it would be nice to configure them in a central location and to not pollute the service container. any interest?

thanks : )

@reinfi
Copy link

reinfi commented Sep 30, 2017

I would say that your application should consist auf multiple modules so there are not so many listeners within the service container to have another plugin manager created.

Also you could simply use another php file to separate your listeners to an own config file.

@abacaphiliac
Copy link
Author

true, i do take advantage of separate modules and PHP files. but in the merged config all services are listed and available from the application service container despite my modular separation.

a listener plugin manager would provide only implementations of the listener interface, so we would gain some type-safety as well as a reduction in the overall number of services registered in the main application service container.

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas/laminas-eventmanager; a new issue has been opened at laminas/laminas-eventmanager#3.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants