dongtun1872 2014-06-19 20:44
浏览 52
已采纳

如何在Phalcon中创建新的注射服务

I'm trying to build a basic "JSON getter" for my Phalcon-based webapp, something like that:

function getJson($url, $assoc=false)
{
$curl = curl_init($url);
$json = curl_exec($curl);
curl_close($curl);
return json_decode($json, $assoc);
}

And of course I would like to make that stuff globally available, possibly as an injectable service. What could be the best way to do that? Should I implement a Phalcon\DI\Injectable? And then, how can I include the new class and feed it to the DI?

Thanks!

  • 写回答

1条回答 默认 最新

  • duanjing9739 2014-06-19 21:00
    关注

    You could extend Phalcon\DI\Injectable but don't have to. A service can be represented by any class. The docs pretty well explain how to work with the dependency injection in general and specifically with Phalcon.

    class JsonService 
    {
        public function getJson($url, $assoc=false)
        {
            $curl = curl_init($url);
            $json = curl_exec($curl);
            curl_close($curl);
            return json_decode($json, $assoc);
        }
    }
    
    $di = new Phalcon\DI();
    
    //Register a "db" service in the container
    $di->setShared('db', function() {
        return new Connection(array(
            "host" => "localhost",
            "username" => "root",
            "password" => "secret",
            "dbname" => "invo"
        ));
    });
    
    //Register a "filter" service in the container
    $di->setShared('filter', function() {
        return new Filter();
    });
    
    // Your json service...
    $di->setShared('jsonService', function() {
        return new JsonService();
    });
    
    // Then later in the app...
    DI::getDefault()->getShared('jsonService')->getJson(…);
    
    // Or if the class where you're accessing the DI extends `Phalcon\DI\Injectable`
    $this->di->getShared('jsonService')->getJson(…);
    

    Just pay attention to get / set vs. getShared / setShared, there are services that may cause problems if created multiple times over and over again (not shared), e.g., take a lot of resources when instantiated. Setting service as shared ensures it's created only once and the instance is reused there after.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 python+selenium,在新增时弹出了一个输入框
  • ¥15 苹果验机结果的api接口哪里有??单次调用1毛钱及以下。
  • ¥20 学生成绩管理系统设计
  • ¥15 来一个cc穿盾脚本开发者
  • ¥15 CST2023安装报错
  • ¥15 使用diffusionbert生成文字 结果是PAD和UNK怎么办
  • ¥15 有人懂怎么做大模型的客服系统吗?卡住了卡住了
  • ¥20 firefly-rk3399上启动卡住了
  • ¥15 如何删除这个虚拟音频
  • ¥50 hyper默认的default switch