This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi all, I have found very useful tips on this forum about part II. I'm deciding what kind of facade will be presented to the client to hide the complexity of distributed components. I have started using this appoach:
Some other guys on this forum have used Session Facade rather then the Business Delegate pattern. I wonder if they can be used together or one exclude the other.... IMHO I cannot see a real difference between this two patterns.... Thanks Rol
The Business Delegate acts as a client-side business abstraction in web tier. It provides an abstraction and hide the implementation of accessing business services. Using a Business Delegate reduces the coupling between presentation-tier clients and the system's business services.
The Session Facade abstracts the underlying business object interactions and provides a service layer that exposes only the required interfaces. It is located in business logic tier.
So the two patterns can be used together without conflict.