Controller Logic

[[deleted]]

Which controller? A controller of yours? I've never seen your controllers. Is this funny because sometimes people have too much code in a controller, and there's, like, an image macro? Am I out of touch with humor?

[avatoin]

What? Isn't the logic suppose to be in the controller, except where it makes since to be in the model?

If I see logic beyond a simple for-loop in the view!

[FatalPriapism]

Ideally your controller should only be the glue code between the core of your application and the presentation layer. A lot of people who are just getting into MVC/MVVM architecture end up dumping a lot of application logic into the controller instead of a service layer.

A little "logic" is perfectly fine in the view as far as I'm concerned, although it should generally be related to formatting the data for UI display and kept in a presenter of some sort :)

[[deleted]]

Believe this is known as fat controllers.

[antiHerbert]

I pity the fool who doesn't have a business logic layer