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.
So far I believe the following is an example of a separated interface pattern.
Some questions regarding Separated interface pattern and n layered design.
I have read that the job of the service layer is to provide services to the business layer. Theoretically Are domain objects
suppose to be available to the other layers or are they just suppose to be available to the service layer ?
Joined: Oct 16, 2011
Since i was told that Domain objects are not allowed to have methods or functionalities in a different thread as this would oppose the single responsibility principle a lot has been clarified. The only question that remains is why would the interface have any relation at all with the domain objects then ?