All geek questions in one place

Should the user interface project type be considered in the implementation of the domain model?

Hmm, the question is in the name :). Just some thoughts on the problem ...

I am thinking about the domain models of my application. I found that the state template suits me, because I have a business object that changed its state, and the states are in strict order, there are also a number of operations whose logic depends on the state.
However, I know that my user interface will be a web application. Since web applications do not have a status (in their general implementation), the state will be changed only once, and I will not have all the advantages of the state template. I don’t even need to change StateObject in someAction in such a web scenario.

So maybe it’s better to just create state order rules and not use a state template?

+3
source share
1 answer

. . , , ; , .

+4

Source: https://habr.com/ru/post/1784894/

More articles:


All Articles