Example: read a local shared object when user logs on, and send value
from local shared object to back-end. The only example I have found of
Cairngorm executing a use case of more than one function is a
Cairnstore version where ValidateCreditCardCommand needs to continue
with CompletePurchaseCommand. It does this by "creating the next
event" i.e. when the Validate command has done its thing, it calls its
executeNextCommand()
method which
public override function executeNextCommand() : void
{
// Create the "next" event.
var purchaseEvent : PurchaseCompleteEvent = new
PurchaseCompleteEvent();
// Dispatch the event.
nextEvent = purchaseEvent;
super.executeNextCommand();
// Clear the event.
nextEvent = null;
}
Is this how one approaches more complex tasks in Cairngorm?
So I would encapsulate the SO read in a event/command/delegate trio,
and then call a value to backend trio by generating its event from the
SO command. If this is the Cairngorm way, would I try to pass the read
in SO value with the command generated event, or should I write the
value to the ModelLocator, and then read it back from the ModelLocator
with the command of the second event? TIA,
Mic
