Login button dispatchs login event, Command - Delegate - Server - Command result has user_id - null user_id = callback to view, non-null user_id loads more data. In this standard Cairngorm app I am using Command extends SequenceCommand to executeNextCommand(); and dispatch loadDataEvent. Because we need view callback I am updating to UM. In reading the UM stuff it looks like
a) Delegate can intercept the response that would normally go the Command b) Presumably Command result can create the loadDataEvent (UM event) and dispatch it. I don't think I want the Delegate to intercept because the returned user_id must be written to a VO in the ModelLocator also, and I am presuming that this is always a job for Command (?). So do I just replace Command result executeNextCommand(); with create and dispatch next event? I am wondering if there is more to this, because the consensus appears to be that standard Cairngorm Command Sequence is ugly and UM is more elegant. TIA, Mic.
