Hi, On Sat, 2008-02-02 at 11:24 +0100, James Pic wrote: > Hi Kore, > > Thanks for your feedback, i agree about error-handling. > > Kore Nordmann wrote: > > As said earlier I still got issues with two sections. My suggestions: > > > > View-management > > --------------- > > > > The controller returns an abstract output object, which then should be > > displayed by the view manager. The view manager receives the output > > object and the abstract request object an can decide on the base of both > > of them which view handler to use. > > > > Example > > ^^^^^^^ > > > > 1. The user requests "/some/file.pdf" > > > > 2. The controller generated the data for this. > > > > 3. The view manager receives a OutputObject with the data, and knows > > from the request structure, that a PDF file has been requested. The > > view manager now select the PDF generator as the view handler and > > calls the right template for the generated output object. > > Why shouldn't the view-handler be selected by the router ?
Because it is a different task, and you may want to overwrite it seperately. It also may depend on the returned content from the controller. I don't see that input and output routing have anything in common - neither the context they work in, nor any methods or similar. So I just see no sense in implementing both in one class. -- Mit freundlichen Grüßen / Med vennlig hilsen Kore Nordmann (GPG: 0xDDC70BBB) eZ Components Developer eZ systems Headquarters tel +49 (0) 231-9742-7750 | fax +49 (0) 231-9742-7751 [EMAIL PROTECTED] | eZ systems | ez.no
signature.asc
Description: This is a digitally signed message part
-- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
