Download the PHP package mouf/pimple-interop without Composer
On this page you can find all versions of the php package mouf/pimple-interop. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mouf/pimple-interop
More information about mouf/pimple-interop
Files in mouf/pimple-interop
Package pimple-interop
Short Description This project is a very simple extension to the Pimple microframework. It adds to Pimple compatibility with the container-interop APIs.
License MIT
Homepage http://mouf-php.com
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package pimple-interop
Pimple-interop
This package contains an extension to the Pimple DI container that makes Pimple 1 compatible with the container-interop API.
How to use it?
Instead of using the Pimple class, you can use the PimpleInterop class. This class extends Pimple.
PimpleInterop implements ContainerInterface. This means
you can access your Pimple entries by using the get and has methods.
PimpleInterop constructor accepts an optional "root" container as a first argument. This means you can chain PimpleInterop with
another container. Dependencies will be fetched from the "root" container rather than from PimpleInterop.
Here is a sample chaining 2 Pimple instances (in the real world, you would rather chain Pimple with a composite container than contains all the DI containers you are working with):
Why the need for this package?
This package is part of a long-term effort to bring interoperability between DI containers. The ultimate goal is to make sure that multiple containers can communicate together by sharing entries (one container might use an entry from another container, etc...)
But can't we already do this using Acclimate?
The excellent Acclimate library can already provide an adapter around Pimple.
The adapter implements the ContainerInterface.
However, the adapter design pattern cannot be used to have Pimple delegate its dependencies fetching to another container. Indeed, to implement this feature, you need to modify the very behaviour of the container, and the adapter design pattern is not always well suited for this.
Also, there are other cases where the adapter design pattern is not enough. For instance, the Silex MVC microframework is directly extending the Pimple class. We could fork the Silex MVC microframework to make it use PimpleInterop instead of Pimple easily. However, it would be almost impossible for Silex to use the adapted Pimple instance from Acclimate (because Silex relies on all the methods of Pimple that are not implemented by the adapter).
