Model View Controller (MVC) Architecture

Go down

Model View Controller (MVC) Architecture  Empty Model View Controller (MVC) Architecture

Post  Admin on Mon Aug 20, 2012 4:37 pm" alt="" />


The model of the CRM WebClient BSPs consists of contexts and context nodes that link the fields of a view to the underlying business layer (the BOL). This linking is referred to as binding.Each data field on a view visualizes an attribute
of a context node.


The view handles the visual output. It is responsible for rendering the output and relevant UI controls, such as data fields and push buttons. All output is received from the controller for rendering. All user input is passed from the view back to
the controller for processing.


The controller handles the interaction logic and provides the connection between a view and a model of a MVC application. A controller receives all keyboard and mouse input from the view. Based on these events, the controller can decide
how to react, for example, by accessing data from the model or triggering the navigation to a different view.

View controllers consist of:

Controller definitions
• Assigned controller classes


Posts : 92
Join date : 2012-01-26

Back to top Go down

Back to top

- Similar topics

Permissions in this forum:
You cannot reply to topics in this forum