Hi Fabien,
Thanks for the precise answer, you did think about nearly everything I
loved to see in Symfony 2 =)
I didn't know about that scopes in spring, thought of their approach
having a configurableBeanFactory and a service container based on
that, the later one implementing all features requiring an instance
pool management. But perhaps "scope" was a valid config key down then
in spring config. But even if the service container is able to deliver
new objects the configurable factory does not need to depend upon the
service container. What I meant with "independent" is that
configurable factorizing objects can be decoupled from configurable
instance managing. A separation somehow like the one between sfContext
and sfFactoryConfigHandler in symfony 1.2.
One last proposal (if you do not have it already included):
What about a fallback for non existing config for a requested instance
that makes the DI frameworks main getter method like "Di::get
('myClass')", or "$container->myClass", behave like "return new myClass
()". So one could safely use the DI framework to retrieve new or
singleton instances without having to care if there even exists a
config. Config is needed only as soon as setting up an instance gets
more complex.
Jan
On 10 Mrz., 09:10, Fabien Potencier <fabien.potenc...@symfony-
project.com> wrote:
> Hi Jan,
>
> Jan Markmann wrote:
> > Hy Fabien,
> > ...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
