Our architecture is currently in (like .net 2.0):
- Data / Unit classes are non-serial
- Many codes in gates / sets in many properties of unit sections (main business verification / business data fresh etc.)
- The logic behind the gates / sets of the database Also use
- Modifying the value in a setter will reflect many other properties / subclasses of the current class
- A "save" method updates the current in-memory object
- Assumptions are handled as a collection from the same class (and automatically refreshed on the recipient / setter basis)
While I think many of the above Problems in Architecture, We Are An Entity Framework, Doubles Usif / RIA want a stateless architecture that is designed / developed using more.
The problem is with the logic behind the gates / sets
What is the best way to accomplish all these
Comments
Post a Comment