When you work with the ZF2 Dependency Injection Container (DiC) when you make multiple requests for an instance of an object you will get the same object back each time. For example, with this
In my previous post about Dependency Injection Container (DiC) configuration I made mention of some more complicated scenarios that you can use to configure your objects. Not that you need help to make it
Configuration is a big reason to use a Dependency Injection Container (DiC). I’ve been doing a lot of playing around with the ZF2 DiC and one of the things that I like about it
One of the cool things in Zend Framework is the Zend_Service layer. What it basically does is provide access to a variety of different service-based… well, services, so that you can easily integrate your application with other services. One example is, of course, Twitter. Often, to connect to various services you need to have an API key that you use to connect. The same is true for Twitter, except for public feed information. What this means is that you can search Twitter for free, with no API, easily.