Don't put businesses logic into the controllers. Controllers should contain application logic. You business logic should be in your models.
On Mon, Nov 3, 2008 at 3:17 PM, monk.e.boy <[EMAIL PROTECTED]>wrote: > > Hi, > > Seeing as we're talking speed, I have a question. One of my controllers is > close to 3,000 lines long, that section of my site has many, many pages. > > Before I ZF'd my site, I just had a lot of .php files. How come I need to > merge all these into one controller? Why does the parser need to parse > hundreds of actions that are never going to be used? > > I would like a "super-controller" to pick the the correct controller for a > page, like the view picks the correct .phtml file. The super-controller > would look at: http://site.com/section/view-stuff/ and load controller > 'section' which would load /application/controllers/actions/view-stuff.php > > Am I missing the point? > > monk.e.boy > -- > View this message in context: > http://www.nabble.com/Controller-Speed-tp20303550p20303550.html > Sent from the Zend Framework mailing list archive at Nabble.com. > >
