On Sat, 23 Feb 2008, James Pic wrote: > Thomas Nunninger wrote: > > Am Freitag, 22. Februar 2008 schrieben Sie: > > > Thomas Nunninger wrote: > > > > - I'm still not sure if we need controller multiplicity at all. I > > > > guess, it's a problem of my limited phantasie/experience as I can't > > > > imagine a situation where I need it. But if we have only one > > > > controller, we only have one output - I guess, this will reduce > > > > complexity. > > > > > > > > The only situation, I can imagine you could use it, is a normal > > > > portal web site, where you have the main content area and e.g. > > > > left/right a menu, some info boxes, ... that are content > > > > independant. But I wouldn't use multiple controllers here because > > > > this is protocoll/interface depending: you want to have a menu in > > > > the HTML frontend but perhaps not in the SOAP or whatever > > > > interface. > > > > > > > > In my opinion, you have one request and this request is handled via > > > > one controller. (If you have a request that includes several > > > > sub-request, you should not handle this via router - that only has > > > > the input to decide on the used controller(s) - but in the > > > > controller, that can call some sub-controllers/-processes. > > > > > > > > Can you give a real world example where you know (from the > > > > beginning/ the request input) that you need more than one > > > > controller? > > > > > > Actually, you'd need one "controller" and several so-called "zones" > > > to build the view of the webportal. > > > > Don't know how other systems solve that. In eZ Publish those "zones" are > > just some templates that are included in page_layout.tpl. Things like > > tree menu or a box with latest news are build via template functions > > that fetch and represent the data. You can argue that this is a little > > bit against strict MVC as there is some logic inside the templates. But > > it is somehow intuitive. Also you do not need to touch the "core" of > > your application or change some configs if you want to add a new > > box/zone. > > > > That's exactly what i'm talking about. The other problem with zones is that > their business-logic is limited to what the template is allowed to use.
Wouldn't it make sense for the actions to make sure those zones end up in the output object? the output object itself can just as well be a container. regards, -- Derick Rethans eZ components Product Manager eZ systems | http://ez.no -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
