Hi Kevin, Am Freitag, 22. Februar 2008 schrieb Kevin Waterson: > On Thu, 2008-02-21 at 10:56 +0100, 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. > > Please allow me to show my newbness and suggest a scenario. > If I have a controller to handle loading, then need to have that > method load another (admin) router/controller how would this be done? > eg: Admin page is loaded. Then select from menu to load admin panel > for blog and then for edit_blog_entry.
thanks for your example. But I guess, this are three requests, that could go like: loading admin -> admin controller (action: perhaps 'index' or 'auth') blog start page -> blog controller (action: probably 'index') new blog entry -> blog controller (action: 'new_entry') Choosing the right controller is the task of the router. But in my opinion there is allways just one controller needed. As James wrote: he thinks mainly about zones/portlets/info boxes/whatever which are shown in one page. I tried to answer this in my other mail. Have a nice day Thomas So each request -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
