On Thu, 17 Nov 2016 06:02:48 -0800 (PST) David Négrier <[email protected]> wrote:
> My whole point is that in order to have containers working side by > side, having a 'composite container' delegating the lookup of entries > to sub-containers is not enough. > You also have to make sure that for any "child container" can > retrieve dependencies from other "child containers". This is only > possible by promoting the DDL design pattern. (see the picture in my > post above and the explanation below for more details). I disagree. :) I think it's an implementation detail. The final user can decide to use a delegating container as a front-facing one, and a non-delegating container "hidden inside". The usage will still be transparent. If a component provides a non-delegating container for its internal use, the outer delegating container doesn't need to know it. It just calls get() on the non-delegating one. The use doesn't care either, as he just calls get() on the delegating one. I can't think of a case in which it would be mandatory for all container to be delegating-aware. Bye. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/20161120122251.64a22332%40namek. For more options, visit https://groups.google.com/d/optout.
