PHP设计模式状态模式
PHP设计模式——状态模式
状态模式当一个对象的内在状态改变时允许改变其行为,这个对象看起来像是改变了其类。状态模式主要解决的是当控制一个对象状态的条件表达式过于复杂时的情况。把状态的判断逻辑转移到表示不同状态的一系列类中,可以把复杂的判断逻辑简化。
UML类图:
角色:
上下文环境(Work):它定义了客户程序需要的接口并维护一个具体状态角色的实例,将与状态相关的操作委托给当前的具体对象来处理。
抽象状态(State):定义一个接口以封装使用上下文环境的的一个特定状态相关的行为。
具体状态(AmState):实现抽象状态定义的接口。
核心代码:
<!--?php /** * Created by PhpStorm---> * User: Jang * Date: 2015/6/10 * Time: 10:34 */ //状态接口 interface IState { function WriteCode(Work $w); } //上午工作状态 class AmState implements IState { public function WriteCode(Work $w) { if($w->hour<=12) { echo 当前时间:{$w->hour}点,上午工作;犯困,午休。 ; } else { $w->SetState(new PmState()); $w->WriteCode(); } } } //下午工作状态 class PmState implements IState { public function WriteCode(Work $w) { if($w->hour<=17) { echo 当前时间:{$w->hour}点,下午工作状态还不错,继续努力。 ; } else { $w->SetState(new NightState()); $w->WriteCode(); } } } //晚上工作状态 class NightState implements IState { public function WriteCode(Work $w) { if($w->IsDone) { $w->SetState(new BreakState()); $w->WriteCode(); } else { if($w->hour<=21) { echo 当前时间:{$w->hour}点,加班哦,疲累至极。 ; } else { $w->SetState(new SleepState()); $w->WriteCode(); } } } } //休息状态 class BreakState implements IState { public function WriteCode(Work $w) { echo 当前时间:{$w->hour}点,下班回家了。 ; } } //睡眠状态 class SleepState implements IState { public function WriteCode(Work $w) { echo 当前时间:{$w->hour}点,不行了,睡着了。 ; } } //工作状态 class Work { private $current; public function Work() { $this->current = new AmState(); } public $hour; public $isDone; public function SetState(IState $s) { $this->current = $s; } public function WriteCode() { $this->current->WriteCode($this); } }
调用客户端测试代码:
//-------------------------状态模式------------------------- require_once ./State/State.php; $emergWork = new Work(); $emergWork->hour = 9; $emergWork->WriteCode(); $emergWork->hour = 10; $emergWork->WriteCode(); $emergWork->hour = 13; $emergWork->WriteCode(); $emergWork->hour=14; $emergWork->WriteCode(); $emergWork->hour = 17; $emergWork->WriteCode(); $emergWork->IsDone = true; $emergWork->IsDone = false; $emergWork->hour = 19; $emergWork->WriteCode(); $emergWork->hour = 22; $emergWork->WriteCode();
适用场景:
1.一个对象的行为取决于它的状态,并且它必须在运行时刻根据状态改变它的行为。
2.一个操作中含有庞大的多分支结构,并且这些分支决定于对象的状态。
优点
1.状态模式将与特定状态相关的行为局部化,并且将不同状态的行为分割开来。
2.所有状态相关的代码都存在于某个ConcereteState中,所以通过定义新的子类很容易地增加新的状态和转换。
3.状态模式通过把各种状态转移逻辑分不到State的子类之间,来减少相互间的依赖。
缺点
导致较多的ConcreteState子类
欢迎关注我的视频课程,地址如下,谢谢。
PHP面向对象设计模式

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

AI Hentai Generator
Generate AI Hentai for free.

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.

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

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.

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.

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.

The advantages of using design patterns in Java frameworks include: enhanced code readability, maintainability, and scalability. Disadvantages include complexity, performance overhead, and steep learning curve due to overuse. Practical case: Proxy mode is used to lazy load objects. Use design patterns wisely to take advantage of their advantages and minimize their disadvantages.

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.
