您的举报已经提交成功，我们将尽快处理，谢谢！
可能(kěnéng)indicateakindofpossibility.可以(kěyǐ)means“can”.F ǒkěyǐhénǐyìqǐqùma?我可以和...
大家还关注
(window.slotbydup=window.slotbydup || []).push({
id: '2081942',
container: s,
size: '1000,60',
display: 'inlay-fix'君，已阅读到文档的结尾了呢~~
Antonio Nicita Simone Sepe..
扫扫二维码，随身浏览文档
手机或平板扫扫即可继续访问
Antonio Nicita Simone Sepe - Universit
224; di Siena
举报该文档为侵权文档。
举报该文档含有违规或不良信息。
反馈该文档无法正常浏览。
举报该文档为重复文档。
推荐理由：
将文档分享至：
分享完整地址
文档地址：
粘贴到BBS或博客
flash地址：
支持嵌入FLASH地址的网站使用
html代码：
&embed src='/DocinViewer--144.swf' width='100%' height='600' type=application/x-shockwave-flash ALLOWFULLSCREEN='true' ALLOWSCRIPTACCESS='always'&&/embed&
450px*300px480px*400px650px*490px
支持嵌入HTML代码的网站使用
您的内容已经提交成功
您所提交的内容需要审核后才能发布，请您等待！
3秒自动关闭窗口DI Factories for Slim controllers - 推酷
DI Factories for Slim controllers
When using classes for route actions in
, I recommend using a single class for each route. However you can use a single class for multiple routes.
To register a class method to a route you pass a string as the route callable where the class name is separate from method by a colon like this:
$app-&get('/list', 'MyController:listAction');
Slim will retrieve
MyController
from the DI container and then call the
listAction
method using the usual signature:
function (Request $request, Response $response, $args = []) : R
If you don't specify a method, then Slim will see if it treat the class as a
, so you can implement
__invoke()
and then register the route like this:
$app-&get('/list', 'MyController');
and Slim will call
MyController::__invoke()
Writing a DI factory for your class
Usually, your controller action will need some dependencies in order to work, such as access to a service layer class, or ORM's entity manager.
To handle this, you should inject the dependency in your controller's constructor by writing a factory for the DI container. This sounds scary and complicated, but a factory is just another way of saying &a function that instantiates an object&. This is the simplest DI container factory we can write for
MyController
// Retrieve container instance
$container = $app-&getContainer();
// Register MyController
$container['MyController'] = function ($c) {
return new MyController();
The closure is the factory and as you can see, it simply returns an new instance of MyController. It is registered with Slim's default DI container by assigning the closure to an array key (
['MyController']
) and it is vital that the string you use here is the same as the string you use before the colon in the route configuration (
'MyController:list'
Injecting the dependencies
To inject the dependencies, we register them with the DI container too as factories and then retrieve them in our controller factory.
Firstly, register a dependency:
$container['DatabaseService'] = function ($c) {
return new DatabaseService();
Now we can use this in our controller factory. To do this note that the factory closure has a parameter,
, which is the DI container itself. This means we can retrieve anything that's registered with the DI container by using the
Hence we update our controller factory like this:
$container['MyController'] = function ($c) {
$dbService = $c-&get('DatabaseService');
return new MyController($dbService);
MyController
constructor now receives our dependency and can store it to a class property ready for use in the route action method like this:
final class MyController
private $dbS
public function __construct($dbService)
$this-&dbService = $dbS
public function listAction($request, $response, $args)
$dataArray = $this-&dbService-&fetchData();
return $response-&withJson($dataArray);
There are numerous advantages to doing this. The main one for me is that there are no surprise dependencies any more. You can look at the constructor and know exactly which classes this class needs to do its job. You can also test it more easily which is beneficial!
I prefer to use one class for each route action as I can ensure that the dependencies that are injected are the correct ones for this action. When using multiple action methods in a controller class, you start needing to inject classes that are only used for just one or two of the actions and this is inefficient, especially if those dependencies are relatively expensive to construct. There are ways around this if you use a more powerful DI container such as Zend-ServiceManager though.
已发表评论数()
已收藏到推刊！
请填写推刊名
描述不能大于100个字符!
权限设置： 公开
仅自己可见
正文不准确
标题不准确
排版有问题
没有分页内容
图片无法显示
视频无法显示
与原文不一致What Is The Difference Between A Neutral Bar And Ground Bar In The Main Electric Box?
Question by&
What is the difference between a neutral bar and ground bar in the main electric box?
+<span id="spN
Answer by&
Ground bar is used for discharging static electric charges that form on the cases and covers of electronic appliances and devices. Static charges may create high voltages, up to 10000 volts. Neutral provides a return path for the current from the supply source, like the negative terminal of a battery
+<span id="spN
Answer by&
Neutral bar is the bar where all
the neutral cables of different circuits (lighting and socket outlets)in an installation are conected/linked to the neutral from the
the supply while the Groung bar is the bar where all the earth/ ground from different circuits in an installation is connected/ to mains earth terminal (consumer's earth electrode)
add your own answer here
You have 50 words left!
add your own comment here
words left!