On 1/2/07, Jaldhar H. Vyas <[EMAIL PROTECTED]> wrote:
That's the Representation part of it. The idea is you can select different views (in MVC talk) based on the MIME type the client prefers.
I'm not sure this part belongs in dispath really. I think its reasonable to assume that the data lookup etc of a runmode like people_GET would be about the same regardless of the format. To me this something done at the end of a runmode or as an overloaded load_tmpl. You may have multiple MIMEs going to the same runmode. For instance you may be producing Atom output, but if someone requested text/xml you'd return Atom anyway since its a form of XML. Conversely you may be using XSLT which converts a generic XML representation into a number of XML formats based on the conneg. I could also see restricting certain formats based on permissions. You could define it in the dispatcher, but you'd have to implement the validation/authention for that in the application object. (This is why I like the _HTTPMETHOD notation defining which methods are supported are in one place -- the application module.) The point I'm trying to make is that there are a lot of posibilities and functionality to capture which could make the relationship between the dispatch and an application module messy and more intetwined then it needs to be. That's why I think that part needs to be handled in the application modules and perhaps supplimented by a utility class or plugin. This works for the HTTP method because you essentially have 4 methods (5 if you want to count HEAD) that won't change -- at least anytime soon. <tim/> -- Timothy Appnel Appnel Solutions http://appnel.com/ Blogcast / Powerful blogging systems made easy http://blogcast.net/ --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
