* Ryan D Johnson <[EMAIL PROTECTED]> [2008-06-23 20:40]: > I've been mulling over whether there's any reasonable way to > fix things to deal with this, but it amounts to any kind of > content negotiation needing to run very early (as part of > dispatch?) and somehow publishing that information to the rest > of the pipeline.
Yes, http://tools.ietf.org/html/rfc2616#section-14.44 HTTP. If you are a web app developer, it is your job to learn it, love it, live it, breathe it. At the very least, study RFC 2616 once to know what’s in there. Most people who try to “solve” some problem with their web app architecture a) do so because they are ignorant of all the facilities of HTTP and b) end up inventing a worse wheel than what HTTP itself provides. The simplicity of HTTP is deceptive; it conceals the deep deliberation that went into choosing *this* form of simplicity vs some other one. (Oh, and this is not a personal comment to you, Ryan – I mean the “you”s above in the general sense.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/