On Tue, 24 Jun 2008, James Pic wrote: > Tobias Schlitt wrote: > > On 06/23/2008 04:50 PM James Pic wrote: > > > > > 1) Should the component supply input filters? > > >> yes, one in a first stage, then many with tieins > > > > We only have UserInput for this purpose, so this would make 1 tiein. > > We might want to make an "authentication filter" tieing Authentication, which > would identify the user making the request. > And probably other filters like that. (That is why i called it plug-ins)
As an example, this filter would identify the user and in some cases, if the user needs to be authenticated, it would change the input object variables to make sure the "login" controller is used instead. > > > Routing > > > ======= > > > 0) Which routed should be developped first? Url, Tree, Regexps, Assertions > > > (railish) ? > > > > Something without a tiein. I think railish and regex sounds like a good > > start. Yeah, they're still different "routers" though. > > > View-manager > > > ============ > > > 0) Should the view-manager implement the same routing system as the > > > router? > > What are the other options? I think I'd like to see an example on how this would work :) > > > 1) Should another object be used to factorized processes that are common > > > the > > > the input and the view-router? > > > > What do you imagine here? > > If the user should develop the router with the same logic than the > view-manager, > maybe we want to have only one router, that decides which controller *and* > view-handler to use. I'd like to have something here that also allows view selection based on user agent strings. For example rendering for mobile devices such as iPhone. regards, Derick -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
