> what is the use of DAO classes in web based
> applications
Here's my take on it - DAO or Data Access Object is basically a class that acts as an itemidiary between 2 different parts of a program. This way neither side has to worry about who they are dealing with. Think of a mortgage broker as a DAO. They worry about the specific interface that a particular bank will require, where as you the user can submit the same information even if you switch banks.
( For some reason I always have a hard time grasping direct logical thoughts, but much easier when they are presented with an analogy).
would any of the more experienced individuals here care to correct any errors in my analogy ?
> > what is the use of DAO classes in web based
> > applications
> Here's my take on it - DAO or Data Access Object is
> basically a class that acts as an itemidiary between
> 2 different parts of a program. This way neither
> side has to worry about who they are dealing with.
> Think of a mortgage broker as a DAO. They worry
> about the specific interface that a particular bank
> will require, where as you the user can submit the
> same information even if you switch banks.
>
> ( For some reason I always have a hard time grasping
> direct logical thoughts, but much easier when they
> are presented with an analogy).
>
> would any of the more experienced individuals here
> care to correct any errors in my analogy ?
*Note that should say intermidiary not itemidiary.
> > *Note that should say intermidiary not itemidiary.
>
> Yup. "intermidiary" is certainly easier to understand
> than "itemidiary". But "intermediary" would be even
> better.
>
> :)
Can I refer you to the TGIF thread ;-) I can't wait to get out of here and climb into a bed and sleep for about 18 hours.
*Edit*
Ps. Does the analogy hold farily well ?
> > what is the use of DAO classes in web based
> > applications
> Here's my take on it - DAO or Data Access Object is
> basically a class that acts as an itemidiary between
> 2 different parts of a program. This way neither
> side has to worry about who they are dealing with.
> Think of a mortgage broker as a DAO. They worry
> about the specific interface that a particular bank
> will require, where as you the user can submit the
> same information even if you switch banks.
WTF?
> ( For some reason I always have a hard time grasping
> direct logical thoughts, but much easier when they
> are presented with an analogy).
So we see.
> would any of the more experienced individuals here
> care to correct any errors in my analogy ?
I think you're describing a Facade. DAO has to do with - wait for it - data access from a data source.
How can you describe what a DAO does without once using the word "data"?
%