RE: Future XSLT extensions. document(). Summary.

["Didier PH Martin" <martind@xxxxxxxxxxxxx>]

Hi,

Paul said:
Very interesting.  Could you please tell me what is the syntax
of XSLT document() you are using to access the database?

Didier replies:
Steve already posted a way to make a sql request to an Oracle server and I
am sure he can provide other examples. I just tested the SQL server this
morning with the following construct

<xsl:apply-templates select="document('localhost/test?sql=select title from
parts-catalog')/catalog/part">

And then have the style sheet to match the elements contained in the <part>
element and produce HTML constructs that are further displayed in both the
Netscape browser and the Microsoft browser. Until Microsoft supports the
document() function, all processing is done server side. But as soon as
Microsoft publish a new version supporting the document() function, the
transformation into HTML will be handled server side for Opera and Netscape
and client side for Explorer. If at least a third of the browsers are
Explorer browsers then, my server resources will be less taxed since 1
request out of three will be handled by the client. Said differently, most
of the job to assemble the content for rendition will be handled by the
client, not the server. And again Paul, I am too tired to argue on this, I
just expressed what experimented and kindly answered to your question. Not
with the intention to judge your position but to simply express the result
of concrete experience, not political fighting.

Cheers
Didier PH Martin
----------------------------------------------
Email: martind@xxxxxxxxxxxxx
Conferences: Web Chicago(http://www.mfweb.com)
             XML Europe (http://www.gca.org)
Book: XML Professional (http://www.wrox.com)
column: Style Matters (http://www.xml.com)
Products: http://www.netfolder.com


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list