Business layer role in data retrieval - criticisms please
Hi, I'm writing a 3 tier product that is set to evolve in functionality over
several years as more modules are developed and optionally integrated. I
therefore need an easily maintainable and manageable design model.
I have a root object in the data layer that deals with all data retrieval
requests and returns typed datasets.
I have a root object in the business layer that does the same.
It seems like a good idea to derive the BL root from the DAL root and
override/add methods to the BL root accordingly.
Does anyone have a good counter argument
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL