Cairngorm is an implementation of several design patterns that form a lightweight ARCHITECTURAL framework. Cairngorm follows the principle of SEPARATING the view and business logic which is known as the Model-View-Controller pattern (MVC).

The Pieces of Cairngorm:

• Model Locator
• View
• Front Controller
• Command
• Delegate
• Service
• Model Locator: Stores all of your APPLICATION’s Value Objects (data) and shared variables, in one place. Similar to an HTTP Session object, except that its stored client side in the Flex interface instead of server side within a middle tier application server.
• View: One or more Flex components (button, PANEL, combo box, Tile, etc) bundled together as a named unit, BOUND to data in the Model Locator, and generating custom Cairngorm Events based on user interaction (clicks, rollovers, drag n drop.)
• Front Controller: Receives Cairngorm Events and maps them to Cairngorm Commands.
• Command: Handles business logic, calls Cairngorm Delegates and/or other Commands, and updates the Value Objects and variables stored in the Model Locator
• Delegate: Created by a Command, they instantiate remote procedure calls (HTTP, Web Services, etc) and hand the results back to that Command.
• Service: Defines the remote procedure calls (HTTP, Web Services, etc) to connect to remote data stores.

Cairngorm is an implementation of several design patterns that form a lightweight architectural framework. Cairngorm follows the principle of separating the view and business logic which is known as the Model-View-Controller pattern (MVC).

The Pieces of Cairngorm: