info/DesignPatternsPHP
1
0
Fork 0
mirror of https://github.com/DesignPatternsPHP/DesignPatternsPHP.git synced 2025-07-31 20:20:15 +02:00
Code Issues Projects Releases Wiki Activity

first, some comments

Browse Source
This commit is contained in:
Trismegiste
2013-05-11 16:57:41 +02:00
parent e325cd9fe6
commit cc93827b8f
1 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
Command/Command.php
View File

@@ -5,11 +5,19 @@ namespace DesignPatterns;
/** /**
* Command pattern * Command pattern
* *
* Purpose: * Purpose: To encapsulate invocation and decoupling
* to build a simple interface for commands that can all be run by just executing a single method they all have in *
* common, often called 'run' or 'execute' * We have an Invoker and a Receiver. This pattern use a "Command" to delegate the
* method call against the Receiver and use the same method "execute".
* Therefore, the Invoker just know to call "execute" to process the Command of
* the client.
*
* The second aspect of ths pattern is the undo(), which undoes the method execute()
* Command can also be agregated to combine more complex commands with minimum
* copy-paste and relying on composition over inheritance.
* *
* Examples: * Examples:
* - A text editor : all events are Command which can be undone, stacked and saved.
* - Symfony2: SF2 Commands that can be run from the CLI are built with just the Command pattern in mind * - Symfony2: SF2 Commands that can be run from the CLI are built with just the Command pattern in mind
* - big CLI tools use subcommands to distribute various tasks and pack them in "modules", each of these * - big CLI tools use subcommands to distribute various tasks and pack them in "modules", each of these
* can be implemented with the Command pattern (e.g. vagrant) * can be implemented with the Command pattern (e.g. vagrant)