PHP设计模式访问者模式
PHP设计模式——访问者模式
访问者模式表示一个作用于某对象结构中的各元素的操作。它使你可以在不改变各元素类的前提下定义作用于这些元素的新操作。
UML类图:
角色:
1.抽象访问者(State):为该对象结构中具体元素角色声明一个访问操作接口。该操作接口的名字和参数标识了发送访问请求给具体访问者的具体元素角色,这样访问者就可以通过该元素角色的特定接口直接访问它。
2.具体访问者(Success):实现访问者声明的接口。
3.抽象元素(Person):定义一个接受访问操作accept(),它以一个访问者作为参数。
4. 具体元素(Man):实现了抽象元素所定义的接受操作接口。
5.结构对象(ObjectStruct):这是使用访问者模式必备的角色。它具备以下特性:能枚举它的元素;可以提供一个高层接口以允许访问者访问它的元素;如有需要,可以设计成一个复合对象或者一个聚集(如一个列表或无序集合)。
核心代码:
<span style="color:#000000;"><!--?php /** * Created by PhpStorm. * User:Jang * Date:2015/6/11 * Tim: 9 :40 */ /*男人这本书的内容要比封面吸引人;女人这本书的封面通常比内容更吸引人 男人成功时,背后多半有一个伟大的女人;女人成功时,背后多半有一个失败的男人 男人失败时,闷头喝酒,谁也不用劝;女人失败时,眼泪汪汪,谁也劝不了 男人恋爱时,凡事不懂也要装懂;女人恋爱时,遇事懂也要装作不懂*/ //抽象状态 abstract class State { protected $state_name; //得到男人反应 public abstract function GetManAction(VMan $elementM); //得到女人反应 public abstract function GetWomanAction(VWoman $elementW); } //抽象人 abstract class Person { public $type_name; public abstract function Accept(State $visitor); } //成功状态 class Success extends State { public function __construct() { $this--->state_name=成功; } public function GetManAction(VMan $elementM) { echo {$elementM->type_name}:{$this->state_name}时,背后多半有一个伟大的女人。 ; } public function GetWomanAction(VWoman $elementW) { echo {$elementW->type_name} :{$this->state_name}时,背后大多有一个不成功的男人。 ; } } //失败状态 class Failure extends State { public function __construct() { $this->state_name=失败; } public function GetManAction(VMan $elementM) { echo {$elementM->type_name}:{$this->state_name}时,闷头喝酒,谁也不用劝。 ; } public function GetWomanAction(VWoman $elementW) { echo {$elementW->type_name} :{$this->state_name}时,眼泪汪汪,谁也劝不了。 ; } } //恋爱状态 class Amativeness extends State { public function __construct() { $this->state_name=恋爱; } public function GetManAction(VMan $elementM) { echo {$elementM->type_name}:{$this->state_name}时,凡事不懂也要装懂。 ; } public function GetWomanAction(VWoman $elementW) { echo {$elementW->type_name} :{$this->state_name}时,遇事懂也要装作不懂。 ; } } //男人 class VMan extends Person { function __construct() { $this->type_name=男人; } public function Accept(State $visitor) { $visitor->GetManAction($this); } } //女人 class VWoman extends Person { public function __construct() { $this->type_name=女人; } public function Accept(State $visitor) { $visitor->GetWomanAction($this); } } //对象结构 class ObjectStruct { private $elements=array(); //增加 public function Add(Person $element) { array_push($this->elements,$element); } //移除 public function Remove(Person $element) { foreach($this->elements as $k=>$v) { if($v==$element) { unset($this->elements[$k]); } } } //查看显示 public function Display(State $visitor) { foreach ($this->elements as $v) { $v->Accept($visitor); } } }</span>
测试客户端代码:
header(Content-Type:text/html;charset=utf-8); //------------------------访问者模式-------------------- require_once ./Visitor/Visitor.php; $os = new ObjectStruct(); $os->Add(new VMan()); $os->Add(new VWoman()); //成功时反应 $ss = new Success(); $os->Display($ss); //失败时反应 $fs = new Failure(); $os->Display($fs); //恋爱时反应 $ats=new Amativeness(); $os->Display($ats);
适用场景及优势:
1) 一个对象结构包含很多类对象,它们有不同的接口,而你想对这些对象实施一些依赖于其具体类的操作。
2) 需要对一个对象结构中的对象进行很多不同的并且不相关的操作,而你想避免让这些操作“污染”这些对象的类。Visitor模式使得你可以将相关的操作集中起来定义在一个类中。
3) 当该对象结构被很多应用共享时,用Visitor模式让每个应用仅包含需要用到的操作。
4) 定义对象结构的类很少改变,但经常需要在此结构上定义新的操作。改变对象结构类需要重定义对所有访问者的接口,这可能需要很大的代价。如果对象结构类经常改变,那么可能还是在这些类中定义这些操作较好。

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











In the Java framework, the difference between design patterns and architectural patterns is that design patterns define abstract solutions to common problems in software design, focusing on the interaction between classes and objects, such as factory patterns. Architectural patterns define the relationship between system structures and modules, focusing on the organization and interaction of system components, such as layered architecture.

The decorator pattern is a structural design pattern that allows dynamic addition of object functionality without modifying the original class. It is implemented through the collaboration of abstract components, concrete components, abstract decorators and concrete decorators, and can flexibly expand class functions to meet changing needs. In this example, milk and mocha decorators are added to Espresso for a total price of $2.29, demonstrating the power of the decorator pattern in dynamically modifying the behavior of objects.

1. Factory pattern: Separate object creation and business logic, and create objects of specified types through factory classes. 2. Observer pattern: allows subject objects to notify observer objects of their state changes, achieving loose coupling and observer pattern.

Design patterns solve code maintenance challenges by providing reusable and extensible solutions: Observer Pattern: Allows objects to subscribe to events and receive notifications when they occur. Factory Pattern: Provides a centralized way to create objects without relying on concrete classes. Singleton pattern: ensures that a class has only one instance, which is used to create globally accessible objects.

TDD is used to write high-quality PHP code. The steps include: writing test cases, describing the expected functionality and making them fail. Write code so that only the test cases pass without excessive optimization or detailed design. After the test cases pass, optimize and refactor the code to improve readability, maintainability, and scalability.

The Guice framework applies a number of design patterns, including: Singleton pattern: ensuring that a class has only one instance through the @Singleton annotation. Factory method pattern: Create a factory method through the @Provides annotation and obtain the object instance during dependency injection. Strategy mode: Encapsulate the algorithm into different strategy classes and specify the specific strategy through the @Named annotation.

The Adapter pattern is a structural design pattern that allows incompatible objects to work together. It converts one interface into another so that the objects can interact smoothly. The object adapter implements the adapter pattern by creating an adapter object containing the adapted object and implementing the target interface. In a practical case, through the adapter mode, the client (such as MediaPlayer) can play advanced format media (such as VLC), although it itself only supports ordinary media formats (such as MP3).

The SpringMVC framework uses the following design patterns: 1. Singleton mode: manages the Spring container; 2. Facade mode: coordinates controller, view and model interaction; 3. Strategy mode: selects a request handler based on the request; 4. Observer mode: publishes and listen for application events. These design patterns enhance the functionality and flexibility of SpringMVC, allowing developers to create efficient and maintainable applications.
