Interesting idea... just a little over complicated maybe :) why not cache the result of the transform when needed, then run it through a sax filter to modify those ((x)html) elements that contain the dynamic content per request?
As the cached html will be the result of a transform we can guarantee it will be well-formed xml. All we need to do is insert some custom elements in the output, such as <myDynamic:name/> and then replace those with the user's details in the sax filter. Cheers andrew From: Joseph Kesselman [mailto:[EMAIL PROTECTED] >I am searching for a solution where I can "cache" the generated HTML-data >of the FAQ (genereated by XSL+XML) and a dynamic part which changes every >request. Building the hole page within a frame is no solution and the FAQ is >only an example. I don't think we have an automated way to do this right now. One solution would be to change your stylesheet so that rather than outputting the result document directly, it outputs a new stylesheet, in which the unchanging information is literal result elements and only the information which actually chages is accessed with XSL instructions. (See, for example, http://www.w3.org/TR/xslt#result-element-stylesheet). You would then run that generated stylesheet as your "production" code, providing it with a source file that reads the sections which actually change. Essentially, you'd be "compiling" the static portions of your stylesheet into literals. (If you need an intro to the concept of using stylesheets to generate/tranform other stylesheets, my two-part article on developerWorks might be helpful; http://www-106.ibm.com/developerworks/xml/library/x-styless1/ and http://www-106.ibm.com/developerworks/xml/library/x-styless2/) --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.483 / Virus Database: 279 - Release Date: 19/05/2003
