cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@infoplanning.com>
Subject Re: XSP -> XSLT -> XSP
Date Tue, 14 Nov 2000 16:42:12 GMT
----- Original Message ----- 
From: "Ugo Cei" <u.cei@cbim.it>
To: <cocoon-users@xml.apache.org>
Sent: Tuesday, November 14, 2000 11:34 AM
Subject: XSP -> XSLT -> XSP


> Is it possibile to have an XSP page that produces another XSP page via
> an XSLT stylesheet and have this second page processed automatically,
> possibly transforming its output again via XSLT to produce HTML?
> 
> This would be something like the clean-page sample, the only difference
> being that the starting page is an XSP document and not a static file.

With Cocoon 1, it would be possible.  With Cocoon 2 it is not possible
by design.  Basically you are forcing the server to do a whole lot more
work than it has to using that approach.  Things that would be better
served with Session variables and state management shouldn't require
a recompile every access.  When you consider that the average compile
on an Athlon 700 with 256 MB of RAM costs you up to 3 seconds per access,
and on an P-II 233 with 128 MB of RAM costs you up to 20 seconds per
access, it really isn't as elegant as it might originally seem.

In short, rethink the purpose of what you are trying to do.  What is
changing between XSP layers?  Is there any way you can merge all logic
into one layer, and then transform out unneeded elements?


Mime
View raw message