On Wed, Mar 7, 2012 at 9:59 AM, Jérôme Étévé <jerome.et...@gmail.com> wrote: > On 7 March 2012 09:49, Pedro Melo <m...@simplicidade.org> wrote: >>> #1 is hard to do because Mason is supposed to be content-type agnostic - >>> usable for HTML generation but also other kinds of content generation.
(this quote is not mine, btw...) > The default filter is defined in the interpreter instance. If you need > to use Mason to generate any type of content, you can perfectly have > different interpreters with different default filters. Anything wrong > with that? Nothing, but its not that simple. If I have a website that generates HTML (normal pages), JSON (AJAX or API) and XML (feeds), should I have several interpreters? And use Plack::Builder to mount each of them on different prefixes? Doable but ugly :) Bye, -- Pedro Melo @pedromelo http://www.simplicidade.org/ http://about.me/melo xmpp:m...@simplicidade.org mailto:m...@simplicidade.org ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
