acelaya

Keybase proof

I hereby claim:

• I am acelaya on github.
• I am acelaya (https://keybase.io/acelaya) on keybase.
• I have a public key whose fingerprint is D736 DA46 5EF0 4830 31D9 0F73 F3FE 9ED9 D900 89FE

To claim this, I am signing this object:

acelaya

<?php
namespace Application\Provider;

use TrascastroACL\Provider\RoleProviderInterface;
use Zend\Authentication\AuthenticationServiceInterface;
use Application\Entity\User;

class MyRoleProvider implements RoleProviderInterface
{
    private $authService;

acelaya

<?php
namespace Application\Service\Factory;

use Zend\ServiceManager\AbstractFactoryInterface;
use Zend\ServiceManager\ServiceLocatorInterface;

class TableGatewayAbstractFactory implements AbstractFactoryInterface
{
    /**
     * Determine if we can create a service with name

acelaya

There are several situations in which it is possible to reuse the same factory to create an object.

Same dependencies

The simplest one is when the objects share the same dependencies. For example, imagine your app uses one TableGateway to manage every DB table. Each one of them will need a database adapter to be injected on it.

Instead of creating one factory for every TableGateway, you can create just one with this content

class TableGatewayFactory

acelaya

docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
docker buildx create --use

# Then docker buildx build should work
# docker buildx build --platform linux/arm/v7,linux/arm64/v8,linux/amd64 .

acelaya

Keybase proof

I hereby claim:

• I am acelaya on github.
• I am acelaya (https://keybase.io/acelaya) on keybase.
• I have a public key ASCgDxMv45xrriDgnKbN1bYIhdxZRB9FXQM97aCN4mm7cAo

To claim this, I am signing this object: