(on Friday, 04 December 2009, 02:39 AM -0800):
> I've read some discussions about the "evil" ActionStack in this forum and
> specifically here:
> http://www.rmauger.co.uk/2009/03/why-the-zend-framework-actionstack-is-evil/
>
> I commented on that (#19).
>
> Now my question is - how do you setup Zend MVC for complex, highly
> configurable websites or portals (not only simple blog applications with
> basic CRUD operations). In particular, websites that consist of many conrete
> pages that make use of (hopefully) reusable components.
>
> For me the best solution is still:
>
> 1. Writing a Zend_Controller_Plugin that hooks into routeShutdown()
> 2. in routeShutdown() compile the set of actions, their parameters,
> templates and layout targets from a given page configuration (xml file,
> database) and the layout file to be used for that page
> 3. Push these actions to the ActionStack
> 4. done
>
> Any other approaches seem not reusable and "hard-coded" for me. I can give
> further details on my implementation if needed. I am just curious how others
> solve the issue "a page consists of several actions and their respective
> views".
I've spoken and blogged a ton on this in the last year. The answer: this
stuff is typically either part of your domain model or part of your view
layer, but has nothing to do with your controllers.
If the reason you're using ActionStack is to re-use business logic...
then that logic should be pushed into your models. If the reason you're
using ActionStack is to re-use view scripts, then simply consume those
view scripts. A judicious use of view placeholders and view helpers can
achieve some tremendous results.
--
Matthew Weier O'Phinney
Project Lead | matthew@zend.com
Zend Framework | http://framework.zend.com/
没有评论:
发表评论