Webdevilopers wrote > I have senn a lot of examples for ZF form handling already like this one: > Zend Framework 2 : Create Simple Upload Form with File Validation > <http://samsonasik.wordpress.com/2012/08/31/zend-framework-2-creating-upload-form-file-validation/> > > > The business logic (handling file upload etc.) takes place inside the > action of the controller:
> > Regarding the "fat model, skinny controller" strategy are these examples > for keeping it simple to understand the sequence of logic? Isn't it best > practice to create a service class to handle the whole process to make the > code re-usable and keep the controller skinny? > > What do you think? It's entirely up to you. I would use a strategy based on the size of your application. If your application is relatively small and has got only few controllers it is ok to have logic inside them. If it's significantly larger then I would use Service layer. ----- Cheers, -- Luke Mierzwa -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Business-logic-inside-controller-tp4657256p4657267.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
