Posted by Tyler Madison | Posted in frameworks | Posted on 08-07-2009
PureMVC is a pretty flexible framework that I have used in a couple projects now, you should check it out. The separation between the three tiers of the application tied together by the “Facade” is a great approach. The framework has its own notification system that works in conjunction with the builtin Flash event dispatcher system. A quick breakdown of the following terminology.
PureMVC Conceptual Diagram
# facade – creates an API that is simplier to use and understand than communicates with much more complex components of the system i.e. the facade handles communication between the Model , View , and Controller tiers. It is also the place to map out you system wide notifications and commands.
#Mediator – facilitates communication between concrete view components and events within the rest of the framework. Basically means that the mediator is responsible for listening to regular “Flash” events from the view component and interpreting how to notify the rest of the system.
#Command – Handles notifications from the system and contains all of the logic for acting upon a given/mapped system notification. The command can retrieve references to other parts of the system and notify and call methods upon them. This is basically where the main application logic lies.
#Proxy – a proxy maintains a reference to a model object that contains some type of data for your application, whether its a calculation, data structure , or XML handling. This is where the data and brains for the application is housed.
More info on PureMVC availiable here!