This talk with the demo on the core of the Cairngorm control process to explain, but also to help readers comb the demo code awareness.
The following diagram is the Caringorm event flow:
In the Operation view is the page of the process will be distributed event, and then by front controller innuendo assigned to the corresponding Command,command to complete the corresponding business process update modellocator data, View automatically updates what is displayed because of the reason that Modellocator (last talked about) is shared.
With this basic process in hand, the reader's understanding of the core control process becomes clearer:
Events: The operation of view or other design-generated event;
Frontcontroller: Is the registration command and the event of the corresponding relationship, to the event for innuendo assigned to the corresponding command;
Command: Conduct business processing, update modellocator (as to how the command section utilizes delegate and service connections to be described in detail in the next lecture);
The reader is well aware of the relationship between the three and the rationale behind the Cairngorm.
Obviously, it corresponds to the following code structure: