Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve read 3 descriptions of the command design pattern:
wikipedia, dofactory and source making.
In all of them, the UML shows a relation between the client to the receiver & the concrete command, but no relation to the invoker.
But in all 3 examples the client is the one that initiates the invoker and call its Execute method.
I think that should be a relation to the invoker as well. Am I missing somthing in here? Maybe even a basic UML knowladge?
That’s probably a limitation of the simple examples. There is no need to have a relationship between the client and the invoker in practice.
The client could serialise the command object and send it to a remote service for execution for example, or the client may add the command to a queue for another thread to de-queue and execute later on.