More about Separated Interface Pattern and layered design
posted 13 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
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 ?
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 ?
Rajesh Khan
Ranch Hand
Posts: 230
posted 13 years ago
-
- Number of slices to send:Optional 'thank-you' note:
-
-
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 ?
| If tomatoes are a fruit, then ketchup must be a jam. Taste this tiny ad: Paul Wheaton's 16th Kickstarter: Gardening playing cards for gardeners and homesteaders https://coderanch.com/t/889615/Paul-Wheaton-Kickstarter-Gardening-playing |