One of the discussions which always comes up and people have asked for over the years is to develop an ASP.Net Web-Application using model-view-controller (MVC).
So what is a Model View Controller (MVC) Framework?
MVC is a framework methodology. The concept of a domain model is technology-neutral. It can even exist only in the abstract -> modeling is a tool - not a religion !!!
- "Models" domain specific representation of the information the application displays and on which it operates. (e.g. we might have a Country class which represents all regions from the Country table inside used RDBMS*)
- "Views" Renders the model into a form suitable for interaction, typically a user interface element or document. Typically this user interface is created off of the model data (for example: we create an Country "Edit" view that populate input boxes to maintain the information based on the current state).
- "Controllers" responsible to act while a handling appears - typically are user actions or service requests and invokes changes on the model. Here its all about to control the response actions.
Scott Guthrie has populated 4 blog entries around this issue:
- ASP.NET MVC Framework - see also the ScreenCast from Scott Hanselman: ScottGu MVC Presentation and ScottHa Screencast from ALT.NET Conference
- ASP.NET MVC Framework (Part 1)
- ASP.NET MVC Framework (Part 2): URL Routing
- ASP.NET MVC Framework (Part 3): Passing ViewData from Controllers to Views
Okey enough to MVC!
Download your copy of SharedCache: http://www.sharedcache.com
SharedCache will soon release session provider, which will assist you to work with SharedCache and ASP.Net Sessions.
Soon i will add some additional thought about how to provide optimistic transactional handling with SharedCache.
SharedCache is free and open source the only way you can see exactly what happens within your application.
* - RDBMS - relational database management system
** - DAO - Data Access Objects
Posts
No comments:
Post a Comment