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:
“An actor must communicate his author’s given message—comedy, tragedy, serio- comedy; then comes his unique moment, as he is confronted by the looked-for, yet at times unexpected, reaction of the audience. This split second is his; he is in command of his medium; the effect vanishes into thin air; but that moment has a power all its own and, like power in any form, is stimulating and alluring.”
—Eleanor Robson Belmont (1878–1979)
“With only one life to live we can’t afford to live it only for itself. Somehow we must each for himself, find the way in which we can make our individual lives fit into the pattern of all the lives which surround it. We must establish our own relationships to the whole. And each must do it in his own way, using his own talents, relying on his own integrity and strength, climbing his own road to his own summit.”
—Hortense Odlum (1892–?)