Hi Jason,
<snip>
> Neat. We can definitely combine different forms of site
> generation. I work with a lot of designers who would still
> be put off by not having direct control over the look. For
> some reason they love formatting #@$%!!! html. But Xalan
> would be awesome the uniform presentation of larger bodies
> of info, like say catalogues.
>
> In your example above, do the macros get passed into
> the resultant HTML and the HTML templates pull in
> info, or do you run the transformation everytime
> the page is hit?
Basically what we do is to pre-compile the .xsl file and cache is for future use
(using Turbine's global cache). Each time a page
is requested we use this pre-compiled .xsl and transform xml to html. The reason for
this being that we use WM to add dynamic
content to the .xml from for example a database.
You get some performance penalty, but not crippling. (JMeter with 10+ threads still
give an average page load time of well under a
second) - The machine is a Win98 Box - 350Mhz Pentium + JDK1.2 + Interbase. Nothing
fancy. I suspect on a 600MHz Linux box
performance will be more than satisfactory.
I'm putting final touches on XmlSite* that we are currently using. I'll post the
final on Tuesday (hopefully Monday :-). There are
still some performance improvements I have to look into...
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
