Hi! On 01/29/2008 01:03 AM James Pic wrote:
> Tobias Schlitt wrote: >> On 01/25/2008 12:34 PM Gaetano Giunta wrote: >>> As far as I am concerned, the C+V should be flexibile enough (or >>> abstracted/away enough) to allow building with extreme ease servers that >>> support different calling-conventions (eg rest,soap,xmlrpc,plain old >>> html etc) for the same functions. >>> This means: >>> - allowing the input abstraction layer to decide upon current >>> module/action to be executed based on any combination of http headers, >>> get params and request payload >> I think this is the thing we need to abstract: The input abstraction >> should abstract from the GET/POST/... data, headers and things, so that >> the router can decide which controller to use. Or did I get you wrong? > Controllers should use an abstracted input object. The input object should be > buildable from differrent request protocols. Yes, that's what I meant. I think this will be tricky to design, thought. >>> - allowing the view to be used for rendering output to be tied either to >>> the action in execution or not (eg tied to the module or to something esle) >> I don't really get this one. Could you elaborate some more here, please? > This looks like controller re-routing to me. I'm not sure. Gaetano, could you explain this to me/us, please? TIA! >>> - allowing to have actions specified as either one class (php file) per >>> action or as one method per action >> This could depend on the router implementation, I think. However, I >> personally would favor to have it defined once, for consistency. > It should be quiet straight-forward to make a controller using classes for > actions anyway. I'm sorry, but I did not get the sense of this sentence. :) What do you mean? Was that a vote for "1 action == 1 class"? Cheers! Toby -- Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer [EMAIL PROTECTED] | eZ Systems AS | ez.no -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
