ramom should not be concerned at all with getting user input into a consumable state. Once input is sent to ramom commands, it is assumed that it is consumable.
Therefore, Ramom::Command objects only need to know about "output dressers" too, just like Ramom::Query objects. This opens up the opportunity to register the dressers with the Operation::Environment` instance, further simplifying setup (and the need for a global constant).
ramomshould not be concerned at all with getting user input into a consumable state. Once input is sent to ramom commands, it is assumed that it is consumable.Therefore,
Ramom::Commandobjects only need to know about "output dressers" too, just likeRamom::Queryobjects. This opens up the opportunity to register the dressers with the Operation::Environment` instance, further simplifying setup (and the need for a global constant).