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:
“Universal empire is the prerogative of a writer. His concerns are with all mankind, and though he cannot command their obedience, he can assign them their duty. The Republic of Letters is more ancient than monarchy, and of far higher character in the world than the vassal court of Britain.”
—Thomas Paine (1737–1809)
“Put out the light, and then put out the light.
If I quench thee, thou flaming minister,
I can again thy former light restore
Should I repent me; but once put out thy light,
Thou cunning’st pattern of excelling nature,
I know not where is that Promethean heat
That can thy light relume.”
—William Shakespeare (1564–1616)