In object-oriented programming, the command pattern is a behavioural design pattern in which an object is used to represent and encapsulate all the information needed to call a method at a later time. This information includes the method name, the object that owns the method and values for the method parameters.
Three terms always associated with the command pattern are client, invoker and receiver. The client instantiates the command object and provides the information required to call the method at a later time. The invoker decides when the method should be called. The receiver is an instance of the class that contains the method's code.
Using command objects makes it easier to construct general components that need to delegate, sequence or execute method calls at a time of their choosing without the need to know the owner of the method or the method parameters.
Read more about Command Pattern: Uses, Structure, Terminology, Example
Famous quotes containing the words command and/or pattern:
“Diamonds may have been a girl’s best friend in an era when a woman’s only hope of having a high family income was to marry a man who was well-off, but today, marketable skills that will enable a woman to command a good income over her lifetime are a better investment.”
—Grace Baruch (20th century)
“Man is eminently a storyteller. His search for a purpose, a cause, an ideal, a mission and the like is largely a search for a plot and a pattern in the development of his life story—a story that is basically without meaning or pattern.”
—Eric Hoffer (1902–1983)