Request-Response Pattern
Scott,
I'm trying to apply the case study to an actual application. In the case study, there is a CreateCustomerRequest and CreateCustomerResponse message. In this case, a customer would be "user". In my application, a user can register themselves or an administrator can create a user from the admin area. When a user registers, they enter minimal data about themselves. When an admin creates a user, that data is added, plus the administrator can add additional details, such as add the user to a list of user groups and change the state of the account (e.g. Pending, Approved, Disapproved).
Having said all this, would it be recommended to create two different sets of Request-Responses: CreateUserRequest, CreateUserResponse and RegisterUserRequest, RegisterUserResponse?
|
