I'm working on an application that will work towards a database
located on the same network. The database will be accessed by
multiple instances, running on diffrent machines in a network, of
the application.
I'm planning to build my application around (or on-top of) a
hierarchical object model, just like the office applications and
so many other applications as well.
The reason for the hierachical object model is to support a
plug-in framework that can be used to extend the application
with additional features, as well as provide automation support.
The question I have is about data-fetching in such an application.
What I mean is that for instance lets say my application support
Employee objects (each object, which ofcourse is a class,
represents an employee) and they are stored in a Employees
(strong-typed) collection. If I also add the top-level object called
Application I'd get something like this
Application
Employees
Employee objects
After giving it some thought (perhaps abit too much and I have
confused myself) I'm abit unsure how to handle it all, data wise.
Should I load all of my employee data from my database into
Employee objects and stick them in my Employees collection,
thus enableing plug-ins to get the data or should I create the
objects on a "need-to-use" basis, how would this be worked
into my app ?
This article uses a nice technique
http://www.c-sharpcorner.com/database/middle_tier.asp
But would it actually work when you need to support plug-ins
as well? If so then I guess I would have to make my collections
in such a way that my enumerator support grabs the data from
the database directly, wouldnt I ?
--
Andreas Håkansson
Student of Software Engineering
andreas (at) selfinflicted.org
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
