On Thursday, July 24, 2003, at 04:53 AM, J�rg Walter wrote:
Am Wednesday, 23. July 2003 18:47, schrieb S Woodside:What if you build an XSLT pipeline, and then bring in the XSP generated
content at the last stage using a <xsl:copy-of
select="document('axkit:foo/bar.xsp')"/> call?
If you did that, you could use XSLT-after-XSP directly. "axkit:" URLs are
tempting, but usually not neccessary. I reccommend to avoid them whenever
possible, just like XSP-after-XSLT. (But for the latter, I know one valid use
case, for the former, I don't)
I'm confused then. I thought that putting cacheable content earlier in the pipeline was better.
simon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
