Thanks for the information below, Ian. Our site is very content-oriented,
and a lot of our business projects are starting to involve things like
co-branding and licensing content, so I'm very interested to hear more
about how you are integrating XSLT and Mason.
Do you generate XML documents in mason and then transform them via XSLT?
Are individual components responsible for their own transformations, or do
you do it all at the end with the whole page?
I agree that HTML::Mason is awesome, and the fact that it parses components
into anonymous perl subs gives it great performance. The other aspect
that's so great is its cacheing system, which can be so easily controlled
programmatically.
At 07:26 AM 7/27/00 -0700, Ian Kallen wrote:
>I'm not going to disparage any of the other templating systems but since
>noone has chimed in for HTML::Mason, I guess I'll have to. Important
>aspects of such a beast is componentization, not just "mail merge"
>behaviors.
>
>Mason components can be just HTML (or XML or fooML) or just Perl or both.
>The "heavy lifting" can be moved to the bottom of a page so you can get
>away from top to bottom processing whih generall demands expressing
>complex code in the middle of HTML. Caching by distilling components down
>into Perl code. In many other respects, the API, the execution and the
>object models are the most empowering.
>
>My current focus is on using Mason as a component system but XSLT when I
>need ad-hoc transformation a la AxKit, Cocoon and other XSLT
>processor-based systems. Mixing AxKit and Mason may sound crazy but each
>has compelling ideas in their architecture.
--
Barry Hoggard
VP of Software Development
e: [EMAIL PROTECTED]
w: http://www.investorama.com
