Shared/NonShared services and documentation

Question

Shared/NonShared services and documentation

Nicola Jun '14

Created Jun '14	Last Reply Dec '15	Replies 3	Views 792	Votes 0

Nicola 7.3k

Jun '14

Hi, I'm new to Phalcon, I'm trying to get a sense about shared/non shared services and what are the best practices when defining services, so, in docs there is this table about "Service Name Conventions" which is pretty self-explanatory and straightforward, on the contrary, in tutorials and answers here in this forum, often for example, DB service is used as non shared as it is otherwise suggested in the service name conventions. The shared db service it makes sense to me, non shared it could, since these two have a different meaning which one is better? or ... is it a thing related with each project architecture?

Thx

vlad4800 · Answer 1 · 2014-06-13T07:08:03-07:00

From the documentation: "Services can be registered as “shared” services this means that they always will act as singletons. Once the service is resolved for the first time the same instance of it is returned every time a consumer retrieve the service from the container"

https://docs.phalcon.io/en/latest/reference/di.html#shared-services

Iliya Garakh · Answer 2 · 2014-07-07T13:36:47-07:00

It's completly depend on your application design. Shared means a singleton — service is created just once and then this instance is used everywhere. In most of cases you can decide not to care about it and define all service as shared. Sometime it can be very important or just a good optimization, anyway it's better to learn a little more about such things as singleton, service pattern, etc and clearly understand how it works.

Jonathan Aaron Steel · Answer 3 · 2015-12-26T19:08:27-07:00

How do you pass an arguments to the shared service?

It seems that this is the only working syntax:

Shared service name: bladeRunner

 $this->di->getBladeRunner([0x0a, 0xff]);

I wanted to avoid refering to DI always and using magic method getSharedService...

so I did it like this:

$di->setShared('bladeRunner', function (){
    class MyOverride extends OriginalClass
    {
        function myCustomOverride($id, $data) {
        //handle data from passed arguments 
        }
    }
    return new MyOverride();
    });

Finally, call the shared service and pass some data to it, this time with much simpler syntax:

 $this->bladeRunner->myCustomOverride([0x0a, 0xff]);