CSC/ECE 517 Fall 2007/wiki3 6 aa: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Topic == | == Topic == | ||
''' | '''Controller Pattern''' | ||
Take the Controller pattern (which we did not cover in class) and catalog the information on it available on the Web. Find good descriptions and good, concise, understandable examples. Tell which you consider the best to present to a class. | Take the Controller pattern (which we did not cover in class) and catalog the information on it available on the Web. Find good descriptions and good, concise, understandable examples. Tell which you consider the best to present to a class. | ||
== What Is == | |||
'''Controller Pattern''' | |||
This is usually also called as Model-View-Controller Pattern. The essence behind this is that when the business logic or data access components are large, a Controller class is introduced between user interface (''View'') and the core logic (''Model''). [[Image:http://upload.wikimedia.org/wikipedia/commons/2/2e/ModelViewControllerDiagram.svg]] | |||
Revision as of 00:11, 20 November 2007
Topic
Controller Pattern
Take the Controller pattern (which we did not cover in class) and catalog the information on it available on the Web. Find good descriptions and good, concise, understandable examples. Tell which you consider the best to present to a class.
What Is
Controller Pattern
This is usually also called as Model-View-Controller Pattern. The essence behind this is that when the business logic or data access components are large, a Controller class is introduced between user interface (View) and the core logic (Model). File:Http://upload.wikimedia.org/wikipedia/commons/2/2e/ModelViewControllerDiagram.svg
