In article <45************ ***********@new sspool2.arcor-online.net>,
ma*******@yahoo .de says...
You need server-side scripting reading out the query string and running
the transformation e.g.
http://example.com/transform.php?xml...lt=viewOne.xsl
then transform.php reads out the file names, runs the transformation and
sends the transformation result to the client.
Curiosity Question:
So, does this mean that the script needs to read the XML file and make
changes to it before sending it to the browser? Is this what is commonly
meant when you say "transform" ?
If that is so, then couldn't one write javascript code that reads the XML
file from wherever it is on the internet and converts (transforms) that
one line to whatever is needed then sends the rest on to the browser? I
know diddly about javascript, but from what I have gathered it can read
files from the internet and it can send HTML to the browser so that the
browser acts as if it just read it directly off of the web site. So, if
the javascript fed the browser an XML file with that one line modified
would the browser then act as if it just read that XML file directly off
of a web site and then do the XSL transformation itself?
Naturally, that would slow down the display because the XML file was
being processed twice but it might work.
Perhaps one could even embed the XML file permanently into the javascript
code. Then the XML would be transmitted at the same time as the
javascript code and would already be on the client's computer. This would
be like writing a program to display a page of text by simply writing a
bunch of cout statements (C++) rather than simply saving and opening the
text file. Naturally, the down side to this is that you no longer have a
true XML file that can be parsed. Maybe you could also write a little
utility that would automatically embed any XML file you wanted into a
similar javascript program to make it easy to generate these javascript
programs. But now I am making it way too complicated.