A library/design and storage question
-
Hi, I´m developing a .NET 2.0 library (dll) which basically is a stamp clock that logs working time and prints job specifications. The application separates UI from logic by a library design approach. I plan to implement both a Windows Form UI and a AJAX UI on the library. The question: What is a good design regarding how to store the logged time entries/data? Shall I store the data in a mdf database or XML files or make an interface an let the application that make use of the library (UI) implement the database interface to enable custom database usage (by doing this every implementation a database setup has to be carried out = bad)? I know this depends on the purpose and usage. Is the mdf approach a good way to store data in both a webapplication and a desktop app? I find this a bit confusing. ^_^ Thanx in advance regards /Christoffer
-
Hi, I´m developing a .NET 2.0 library (dll) which basically is a stamp clock that logs working time and prints job specifications. The application separates UI from logic by a library design approach. I plan to implement both a Windows Form UI and a AJAX UI on the library. The question: What is a good design regarding how to store the logged time entries/data? Shall I store the data in a mdf database or XML files or make an interface an let the application that make use of the library (UI) implement the database interface to enable custom database usage (by doing this every implementation a database setup has to be carried out = bad)? I know this depends on the purpose and usage. Is the mdf approach a good way to store data in both a webapplication and a desktop app? I find this a bit confusing. ^_^ Thanx in advance regards /Christoffer
http://en.wikipedia.org/wiki/Model-view-controller[^] Model The domain-specific representation of the information on which the application operates. The model is another name for the domain layer. Domain logic adds meaning to raw data (e.g., calculating if today is the user's birthday, or the totals, taxes and shipping charges for shopping cart items). Many applications use a persistent storage mechanism (such as a database) to store data. MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the Model.
led mike