Derick Rethans wrote: > On Fri, 20 Jun 2008, James Pic wrote: > > Kore Nordmann wrote: > > > - (HTTP) redirects are also "just" some view structure, which is returned > > > by > > > the controller, and the view actually performs the proper action > > > depending > > > on the context. > > Do we want the controller to set HTTP headers in the output object? > > I'd say that the view-manager should take care of figuring the > > response code by itself. > Yes, I think this should be up to the view/view manager. How do we want that standartized for the output object? Here is a short list of proposals: - $output->status: status identifier, like OK, FAIL, REDIRECT ... - $output->redirect: the redirect object, with variables that should be sent and the controllr name - you-name-it > > However, we might want to standardize some > > common UI needs, like with a list of user-messages or something like > > this: "sorry, you don't have the permission to do something". "Sorry, > > please try again later" ... > Yes, perhaps - although those will never show for normal redirects > obviously. What do we want? Here is a short list of proposals: - A sort of ArrayObject in $input->messages, that would contain ezcMvcMessage, - $input->locale, that would contain the locale string, - $input->user, that would contain the user object that is doing the request, - $input->protocol, that would contain a protocol identifier, you-name-it ... > > > Filters can be set on the controller, which are > > > called first and work on the input - modify, action being run at all ... > > > > Callbacks? Or a filter configuration? How deep do we want this? > > I think that when adding a filter to a controller/default controller, > they should be callbacks to other classes/methods. This allows us to > provide filters in tie-in components (such as for > authentication/identification). Callbacks or filter-objects directly? I ignore how you want to do this, may you supply a high(system)-level example please? > > > The "user" object should be accessible in the view as well, to allow for > > > anonymous/authenticated. > > Do we want a user interface or something like that? (to make the code > > portable > > and testable) > Not sure what you mean here, could you provide an example? Me neither, yet, I'll come back on this later ;) (for certain tieins)
Regards, James. -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
