PHP mode design registration tree mode, PHP mode design_PHP tutorial

php pattern design registration tree pattern, php pattern design

After the first two articles of singleton pattern and factory pattern, we finally come to the last basic design pattern-- Register tree mode.

　What is the registration tree mode?

Of course, the registration tree mode is also called registration mode and registrar mode. The reason why I am pretentious about its name here is because I feel that the name registration tree is easier for people to understand. Like the previous two articles, our article still starts with the name. The registration tree pattern is a pattern design method that registers object instances to a global object tree and picks from the object tree when needed. This reminds me of buying candied haws on a stick when I was a kid. The candied haws seller would stick the candied haws on a big pole and people would take them off when they bought them. The difference is that in the registration tree mode, there will still be some after being picked, and it can be picked many times, but the candied haws will be gone after being picked once. . .

　Why should we use registration tree mode?

The singleton mode solves the problem of how to create a unique object instance in the entire project, and the factory mode solves the problem of how to create an instance object without using new. So what problem does the registration tree mode want to solve? Before considering this issue, we still need to consider the limitations currently faced by the first two models. First of all, the process of creating a unique object in the singleton mode itself also has a judgment, that is, whether the object exists. If it exists, the object is returned; if it does not exist, the object is created and returned. Every time an instance object is created, there must be such a layer of judgment. The factory model considers more the issue of extended maintenance. In general, the singleton pattern and factory pattern can produce more reasonable objects. How to conveniently call these objects? Moreover, the objects created in this way in the project are like scattered soldiers, making it inconvenient for overall management and arrangement. Therefore, the registration tree model came into being. Regardless of whether you generate objects through singleton mode, factory mode, or a combination of the two, they are all "inserted" into the registration tree. When I use an object, I just fetch it directly from the registration tree. This is as convenient and practical as using global variables. And the registration tree pattern also provides a very good idea for other patterns.

How to implement a registration tree?

Through the above description, we seem to have easily found a solution. First we need a class as a registration tree, of course. All objects are "inserted" into the registration tree. This registration tree should be served by a static variable. And this registration tree should be a two-dimensional array. This class should have a method for inserting object instances (set()), and correspondingly there should be a method for undoing object instances (_unset()). Of course, the most important thing is to have a method to read the object (get()). With these, we can happily complete the registration tree mode~~~

Now let’s make a small combination of the three modes. Simply creating an instance object is far less complicated, but when applied to large projects, the convenience is self-evident.

<?<span>php<br />//创建单例
</span><span>class</span><span> Single{
    </span><span>public</span> <span>$hash</span><span>;
    </span><span>static</span> <span>protected</span> <span>$ins</span>=<span>null</span><span>;
    </span><span>final</span> <span>protected</span> <span>function</span><span> __construct(){
        </span><span>$this</span>->hash=<span>rand</span>(1,9999<span>);
    }

    </span><span>static</span> <span>public</span> <span>function</span><span> getInstance(){
        </span><span>if</span> (self::<span>$ins</span><span> instanceof self) {
            </span><span>return</span> self::<span>$ins</span><span>;
        }
        self</span>::<span>$ins</span>=<span>new</span><span> self();
        </span><span>return</span> self::<span>$ins</span><span>;
    } 
}

//工厂模式
</span><span>class</span><span> RandFactory{
    </span><span>public</span> <span>static</span> <span>function</span><span> factory(){
        </span><span>return</span> Single::<span>getInstance();
    }
}

//注册树
</span><span>class</span><span> Register{
    </span><span>protected</span> <span>static</span> <span>$objects</span><span>;
    </span><span>public</span> <span>static</span> <span>function</span> set(<span>$alias</span>,<span>$object</span><span>){
        self</span>::<span>$objects</span>[<span>$alias</span>]=<span>$object</span><span>;
    }
    </span><span>public</span> <span>static</span> <span>function</span> get(<span>$alias</span><span>){
        </span><span>return</span> self::<span>$objects</span>[<span>$alias</span><span>];
    }
    </span><span>public</span> <span>static</span> <span>function</span> _unset(<span>$alias</span><span>){
        </span><span>unset</span>(self::<span>$objects</span>[<span>$alias</span><span>]);
    }
}

Register</span>::set('rand',RandFactory::<span>factory());

</span><span>$object</span>=Register::get('rand'<span>);

</span><span>print_r</span>(<span>$object</span>);

　

At this point, the introduction of the three modes of design is completed. Various pattern designs themselves will complement each other. When introducing other patterns in the future, one or more other design patterns will be used more or less.

It doesn’t matter if you don’t understand a certain model. I believe that with the in-depth programming, there will be a surprise of sudden enlightenment. I hope you will make progress with me.

　

Series of articles:

　 PHP pattern design singleton pattern

　PHP pattern design factory pattern

　PHP pattern design registration tree pattern

　

http://www.bkjia.com/PHPjc/1048721.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/1048721.htmlTechArticlePHP pattern design registration tree pattern, php pattern design finally follows the first two articles of singleton pattern and factory pattern. The last basic design pattern is ushered in-the registration tree pattern. What is registration...