Actually that should say "one of the problems..."
Most templating systems out there work in one of two ways:
1. a bi-directional manner, where you have both systems calling into the
template, and the template calling out to code. Take for example TT, you
can have a module call the template
Matt Sergeant wrote:
To picture this better I imagine it as a forward moving pipeline, from
initial "resource" (the XML file, or whatever the URL maps to), to
delivering the file:
Res --- Process --- Process --- Process --- Delivery
I think this is an interesting way of looking at
