Recommend this page to a friend! |
Classes of Duong Huynh Nghia | PHP Slim Framework 3 Modular Application | libraries/vendor/container-interop/container-interop/docs/Delegate-lookup.md | Download |
|
DownloadDelegate lookup featureThis document describes a standard for dependency injection containers. The goal set by the delegate lookup feature is to allow several containers to share entries. Containers implementing this feature can perform dependency lookups in other containers. Containers implementing this feature will offer a greater lever of interoperability with other containers. Implementation of this feature is therefore RECOMMENDED. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119][]. The word [RFC 2119]: http://tools.ietf.org/html/rfc2119
In a dependency injection container, the container is used to fetch entries. Entries can have dependencies on other entries. Usually, these other entries are fetched by the container. The delegate lookup feature is the ability for a container to fetch dependencies in another container. In the rest of the document, the word "container" will reference the container implemented by the implementor. The word "delegate container" will reference the container we are fetching the dependencies from.
A container implementing the delegate lookup feature:
When a container is configured to use a delegate container for dependencies:
Important: By default, the dependency lookups SHOULD be performed on the delegate container only, not on the container itself. It is however allowed for containers to provide exception cases for special entries, and a way to lookup into the same container (or another container) instead of the delegate container.
This feature is not tied to any code, interface or package. |