Comments on: Keeping your CakePHP Controllers Clean

By: kekgvcvk

kekgvcvk — Fri, 19 Feb 2010 01:58:58 +0000

kekgvcvk…

By: eve isk

eve isk — Tue, 08 Dec 2009 09:11:57 +0000

I love it.

By: last chaos money

last chaos money — Sat, 22 Aug 2009 03:06:28 +0000

Good post,This was exactly what I needed to read today! I am sure this has relevance to many of us out there.

By: last chaos money

last chaos money — Fri, 26 Jun 2009 01:15:35 +0000

This is a great article. I’m new to blogging but still learning. Thanks for the great resource.

By: Juan

Juan — Mon, 16 Mar 2009 03:31:54 +0000

Hey man, now you are actually using MVC as it is meant to be. Controllers just control user input nothing else. The brain of the app are the models.

By: Alvaro

Alvaro — Mon, 16 Mar 2009 01:59:26 +0000

Following REST architecture helps to made apps with skinny controllers and don’t think too much on how your actions have to be named.

By: Daniel Hofstetter

Daniel Hofstetter — Sun, 15 Mar 2009 17:02:41 +0000

This practice is usually called “Skinny controllers, fat models” and is a best practice for writing CakePHP (resp. MVC) applications.

By: Jamie

Jamie — Sun, 15 Mar 2009 15:14:28 +0000

My reasoning would be to simply segregate the code more. The controller is the middle man for data and display, why not make it the middle man for logic as well?

By: Jimmy Bourassa

Jimmy Bourassa — Sun, 15 Mar 2009 13:02:41 +0000

Great article, I must admit I feel quite similar to what you described haha!

I’m just unsure about the component part – wouldn’t a component be handy only in a case where your logic must be widely usable and generic? I don’t see why you would write every kind of logic in the Component. Any explanation would be greatly appreciated

By: Marek Kebza

Marek Kebza — Sun, 15 Mar 2009 09:52:25 +0000

I have same goal as you. But i got used to even simple calls to find(‘all’) hide in model as a method. Because you never know when conditions, ordering and so on will change. Then you don’t have to refractor and you are keeping all data manipulation logic hidden inside a model.