MVC: Controller or Library

Question

I'm very new to MVC, and I would like to get a clarification about the function of a controller.

Imagine this primitive example:

I have 2 models and 1 controller, that gets data from both models, and I have to do a very complicated calculation with these 2 data packages. (Then give the result to a view.)

My question is:

Should I put this complicated calculation into the controller, or should I put it outside into a library? In more general form:

Am I allowed to make calculations inside a controller, or is it a bad practice?

http://stackoverflow.com/questions/8735466/fat-model-thin-controller-vs-service-layer — Mike C., Mar 14 '13 at 18:00
@tereško how do you mean it? I use php, and everywhere I saw the implementation of mvc, models were classes. — Balazs Sipos, Mar 16 '13 at 05:45
@BalazsSipos , only type of frameworks which refer to "models" as classes are Rails clones. And it was never an MVC framework to begin with. — tereško, Mar 16 '13 at 06:03

score 0 · Answer 1 · edited May 23 '17 at 12:00

0

Controllers are the easy place to put this kind of logic, and become easily cluttered. Separation of concerns would take you down the path of implementing a service layer.

edited May 23 '17 at 12:00

Community

1
1

answered Mar 14 '13 at 18:00

felickz

4,292
3
33
37

score 0 · Answer 2 · answered Mar 14 '13 at 18:01

0

Controllers should be as light as possible and have few dependencies. Your Model should handle business logic like this although you may want to put it in its own library. If you do put it in a different library, call it from the model.

answered Mar 14 '13 at 18:01

marteljn

6,446
3
30
43

MVC: Controller or Library

2 Answers2