DELPHI MVC (ECB)

Good I particularly never developed in Mvc with Delphi, but I found this example on the web handout Delphi Mvc, to develop in Mvc basically is more the separation of the objects in layers for this the whole project will have to be Object Oriented manipulating and returning objects like qualuqer other language until normal ai, the only thing that the way to create, inherit, overload in delphi is a little different so many are scared by it.

The MVC model is intended for building interfaces ( http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller ) and not of the entire application architecture. Other models may also reach the same result and the arguments you put forward will not necessarily be achieved solely by making use of this model.

Issues regarding business rules and persistence are not covered by MVC, since its primary purpose is to build business rules and persistence objects. user interaction that allow the use of unit tests during their implementation.

It is considered a mistake to implement business rules on a controller as much as it would be wrong to implement them on a Form and for the same reasons.

The implementation of business rules can be located in different parts of the application depending on the chosen architectural model. For example, if you are going to make use of DDD (Domain-Driven Design) then the rules of business will be implemented in domain classes and service classes, while persistence will be managed by repositories, making or not using an automatic persistence system.

There is a product in https://code.google.com/p/delphimvcframework /

See the MVCBr model-a delphi/MVC framework. http://www.tireideletra.com.br through a set of wizards show how to apply in practice the concept in app in the MVC standard.