No that's what the model is for. The controller is just for handling framework specific input. It takes the framework specific part, puts it in a form that th

No that's what the model is for. The controller is just for handling framework specific input. It takes the framework specific part, puts it in a form that the business logic can understand (eg: business logic shouldn't even know what a mouseEvent is), and hands it off to the model's business logic to handle.