Behavioral pattern

In software engineering, behavioral design patterns are design patterns that identify common communication patterns between objects and realize these patterns. By doing so, these patterns increase flexibility in carrying out this communication.

Examples of this type of design pattern include:

• Chain of responsibility pattern: Command objects are handled or passed on to other objects by logic-containing processing objects
• Command pattern: Command objects encapsulate an action and its parameters
• "Externalize the Stack": Turn a recursive function into an iterative one that uses a stack.^[1]
• Interpreter pattern: Implement a specialized computer language to rapidly solve a specific set of problems
• Iterator pattern: Iterators are used to access the elements of an aggregate object sequentially without exposing its underlying representation
• Mediator pattern: Provides a unified interface to a set of interfaces in a subsystem
• Memento pattern: Provides the ability to restore an object to its previous state (rollback)
• Null Object pattern: designed to act as a default value of an object
• Observer pattern: aka Publish/Subscribe or Event Listener. Objects register to observe an event which may be raised by another object
  • Weak reference pattern: De-couple an observer from an observable.^[2]
• Protocol stack: Communications are handled by multiple layers, which form an encapsulation hierarchy.^[3]
• State pattern: A clean way for an object to partially change its type at runtime
• Strategy pattern: Algorithms can be selected on the fly
• Specification pattern: Recombinable Business logic in a boolean fashion
• Template method pattern: Describes the program skeleton of a program
• Visitor pattern: A way to separate an algorithm from an object
• Single-serving visitor pattern: Optimise the implementation of a visitor that is allocated, used only once, and then deleted
• Hierarchical visitor pattern: Provide a way to visit every node in a hierarchical data structure such as a tree.
• Scheduled-task pattern: A task is scheduled to be performed at a particular interval or clock time (used in real-time computing)

See also

• Structural pattern
• Creational pattern
• Concurrency pattern

References

1. ^ http://c2.com/cgi/wiki?ExternalizeTheStack
2. ^ http://c2.com/cgi/wiki?WeakReferencePattern
3. ^ http://c2.com/cgi/wiki?ProtocolStack