定制 mouf/prefixer-container 二次开发

按需修改功能、优化性能、对接业务系统,提供一站式技术支持

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

mouf/prefixer-container

Composer 安装命令:

composer require mouf/prefixer-container

包简介

This package contains a really minimalist dependency injection container that acts as a proxy in front of a target container. Its goal is to prefix all instances names in the target container.

README 文档

README

Latest Stable Version Latest Unstable Version License Scrutinizer Code Quality SensioLabsInsight Build Status Coverage Status

This package contains a really minimalist dependency injection container that can be used to prefix all identifiers in a container. Prefixer-container is compatible with container-interop and is meant to be used in conjunction with other containers. By itself, Prefix-container does not store any entry. It can only be used to wrap an existing container.

You can use PrefixerContainer to put all identifiers of a container in a namespace.

Installation

Before using PrefixerContainer in your project, add it to your composer.json file:

$ ./composer.phar require mouf/prefixer-container ~1.0

Usage

Imagine you have 2 containers living side-by-side, and a composite container (we will call it the "root" container) is joining them. Now, both containers declare a same instance named "dbConnection".

If you want to keep access to both instances through the root container, you have a problem, because you have a naming collision. Of course, you can rename one of those instances, but if the containers are provided by third party libraries, that might not be possible.

The issue

So what you need to do is to rename the instances of one of the containers so that there is no more conflict. This is where the PrefixerContainer kicks in.

Solution 1

By wrapping your containers inside a PrefixerContainer, you can change the name of the instances to the outside world.

Here is a sample code demonstrating the code above:

use Mouf\PrefixerContainer\PrefixerContainer;
use Acclimate\Container\CompositeContainer;
use Interop\Container\ContainerInterface;
use Mouf\Picotainer\Picotainer;


$rootContainer = new CompositeContainer();

// We use Picotainer, a minimalistic container for this demo.
$containerA = new Picotainer([
    "dbConnection" => function () { return new DbConnection(...); },
]);

$containerB = new Picotainer([
    "dbConnection" => function () { return new OtherDbConnection(...); },
]);


$rootContainer->addContainer(new PrefixerContainer($containerA, 'A.')));
$rootContainer->addContainer(new PrefixerContainer($containerB, 'B.')));

// Get 'dbConnection' from container A:
$dbConnectionA = $rootContainer->get('A.dbConnection');

// Get 'dbConnection' from container B:
$dbConnectionB = $rootContainer->get('B.dbConnection');

// This will throw a NotFoundException:
$willFail = $rootContainer->get('dbConnection');

Working with delegate lookup containers

If the container you are wrapping is implementing the delegate lookup feature (it should!), you will face another problem.

When you use the delegate lookup feature, the dependencies are fetched from the root container. Now, the name of the dependencies has changed because of the PrefixerContainer!

Just image a container with a service that uses the dbConnection:

A container with a dependency

What if we wrap this container in a PrefixerContainer? If we query the A.myService entry (1), the container will delegate to the rootContainer the lookup of the dbConnection entry. Now, this is a problem, because it should query the A.dbConnection entry.

Delegate lookup issue

In order to fix this, the prefixer-container comes with a DelegateLookupUnprefixerContainer class. This is a wrapper you will use to wrap the delegate lookup container. When the get method of the wrapper is called, it will first try to get the instance with the prefix, and if it fails, it will try to get the instance without the prefix.

Delegate lookup solved

If we query the A.myService entry (1), , the container will delegate to the rootContainer the lookup of the dbConnection entry (2). This goes through the DelegateLookupUnprefixerContainer first that will add the "A." prefix (3). The lookup goes through the root container again, then the prefixer container that strips the "A." and finally, the dependency dbConnection is solved. Job's done!

Here is a sample code demonstrating the code above:

use Mouf\PrefixerContainer\PrefixerContainer;
use Acclimate\Container\CompositeContainer;
use Interop\Container\ContainerInterface;
use Mouf\Picotainer\Picotainer;

$prefix = "A.";

$rootContainer = new CompositeContainer();

// We use Picotainer, a minimalistic container for this demo.
$container = new Picotainer([
    "dbConnection" => function () { return new DbConnection(...); },
    // The myService service requires the 'dbConnection'
    "myService" => function (ContainerInterface $c) { return new MyService($c->get('dbConnection')); },
], new DelegateLookupUnprefixerContainer($rootContainer, $prefix));

// In the root container, we add a prefixed version of the container
$rootContainer->addContainer(new PrefixerContainer($container, $prefix));

$service = $rootContainer->get('myService');

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...)

mouf/prefixer-container 适用场景与选型建议

mouf/prefixer-container 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 13 次下载、GitHub Stars 达 3, 最近一次更新时间为 2015 年 01 月 31 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「dependency injection」 「di」 「container-interop」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

我们在过去多个企业项目中使用过 mouf/prefixer-container 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 mouf/prefixer-container 我们能提供哪些服务?
定制开发 / 二次开发

基于 mouf/prefixer-container 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 13
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 3
  • 点击次数: 24
  • 依赖项目数: 0
  • 推荐数: 0

GitHub 信息

  • Stars: 3
  • Watchers: 16
  • Forks: 0
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2015-01-31