Flow of Control

The flow of control begins at the controller, moves through the use case, and then winds up executing the presenter.

Register Flow of Control

1. A request is received by the CustomersController then the Post action is invoked.
2. The Post action creates a RegisterInput message then the Register use case is called.
3. The Register use case creates a Customer and an Account entities. Repositories are called, the RegisterOutput message is built and sent to the RegisterPresenter.
4. The RegisterPresenter builds the HTTP response message.
5. The CustomersController asks the presenter for the current response message.

Get Customer Details Flow of Control

1. A request is received by the CustomersController then the GetCustomer action is invoked.
2. The GetCustomer action creates an GetCustomerDetailsInput message then GetCustomerDetails use case is called.
3. The GetCustomerDetails use case asks the repositories about the Customer and the Account. It could call the NotFound or the Default output port of the GetCustomerDetailsPresenter if it exists or does not.
4. The GetCustomerDetailsPresenter builds the HTTP response message.
5. The CustomersController asks the presenter for the current response.