Add setAliases and setFactories methods branch 2.7

[malinink]

We should add methods to branch 2.7 in order to change other components that to use them before we migrate to SM3.

More information could be found here #112

All components listed in symmetric PR #114

[Ocramius]

Disagree with this approach. This API should at least be private and used only by internal zendframework/zend-servicemanager components. public is a no-go in my opinion, especially after all the effort put into reducing the surface of interaction with the ServiceManager

[malinink]

@Ocramius
If that methods will be protected or private then we could not use them outside class.
Both of methods made for the same as a function setFactory and setAlias (and that method are public).

The reason of creation new methods is new SM3, where it is better to add all aliases or factories at once due to performance issues.

Maybe there are any other ways to do that? (all discussion is here #112 and here #122)

[Ocramius]

The reason of creation new methods is new SM3, where it is better to add all aliases or factories at once due to performance issues.

I understand that. I wonder if we have a way to avoid that, and instead merge configs upfront (which would remove an entire set of problems in this space completely)

[weierophinney]

Use configure() is you want to do multiple aliases or factories at once.
It's not BC, bit works for v3.
On Jun 5, 2016 3:43 PM, "Marco Pivetta" notifications@github.com wrote:

The reason of creation new methods is new SM3, where it is better to add
all aliases or factories at once due to performance issues.

I understand that. I wonder if we have a way to avoid that, and instead
merge configs upfront (which would remove an entire set of problems in this
space completely)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#115 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AABlVyAivURX1pWBgsXDjQ4OGNjBiC9yks5qIzUCgaJpZM4IBZRY
.

[malinink]

@Ocramius @weierophinney
As I see, these PR already exist in all depend components.

• fix performance issues using sm3 configure() zend-form#77
• use sm3 configure when possible zend-i18n#47

So it is better to close both my PR (#114 #115), and issue (#112).

[Ocramius]

Closing as per discussion

Moving on to:

• fix performance issues using sm3 configure() zend-form#77
• use sm3 configure when possible zend-i18n#47