Hi! On 01/29/2008 01:09 AM James Pic wrote:
> Tobias Struckmeier wrote: >>>> - Input abstraction (also see above) >>>>> - Routing >>>>> - Controllers >>>>> - Output abstraction >> I want to add here: >> - A standard "URL building mechanism" should be there that helps to >> build the urls for the specific contexts (eg. AJAX), make redirections >> etc. > Isn't it possible to do with Url component natively ? Partly, yes. But the idea is to not rely on Url for the Mvc in a first place, but to possibly offer a tie-in (later). Therefore we need to abstract that somehow. I'd suggest to go with GET parameters for the very basic implementation and offer a mechanism that makes use of Url through a tie-in. >> - There really should be a fallback controller when no >> controller/action is found or a rerouting on another controller should >> be done. > I'm unsure if the component should supply a 404 default controller, but mvc= > tools > guide should definitively describe the procedure to it. No, a 404 and an incorrect action are 2 different things, IMO. A 404 occurs of the requested document does not exist. If the action is faulty, this usually means that the accessed file is correct, but a submitted parameter is incorrect. So this is an error that should be handeled by the application. And actually you don't want to display a 404 to the user anyway. :) For more comments, please see my reply to Tobias' mail directly. Regards, 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
