G
guhar1
A few design issues:
1. If I decide to implement an interface between my "business object
layer" and my "data access layer", so as to protect the BOL from
changes in DAL, do I provide ONE interface class containing all the
other required interface, or do I expose several separate interface to
the DAL? (Seems conceptualy cleaner to provide on interface class, and
stuff everything I need in it)
2. I i decide to provide an "object factory", so as to create my object
on the fly using a config file (Oracle vs SqlServer) should the factory
be encapsulated in the interface, or should it be at the same level as
the interface (BOL-DAl), or shoud it be global to all layers?
Thanks
1. If I decide to implement an interface between my "business object
layer" and my "data access layer", so as to protect the BOL from
changes in DAL, do I provide ONE interface class containing all the
other required interface, or do I expose several separate interface to
the DAL? (Seems conceptualy cleaner to provide on interface class, and
stuff everything I need in it)
2. I i decide to provide an "object factory", so as to create my object
on the fly using a config file (Oracle vs SqlServer) should the factory
be encapsulated in the interface, or should it be at the same level as
the interface (BOL-DAl), or shoud it be global to all layers?
Thanks