[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Didier's lab report

• From: Kay Michael <Michael.Kay@i...>
• To: "'martind@n...'" <martind@n...>,"Arnold, Curt" <Curt.Arnold@h...>, xml-dev@x...
• Date: Thu, 27 Jul 2000 23:51:58 +0100

It's entirely feasible for an XSLT processor to recognize at compile time
any calls of document() that can be resolved statically, and to generate
code in the compiled stylesheet that causes the download of these documents
to start asynchronously as soon as stylesheet execution starts. This isn't
true in the example cited, because the absolute URI of the required document
depends on the base URI of the current node in the source document.

Mike Kay

> -----Original Message-----
> From:	Didier PH Martin [SMTP:martind@n...]
> Sent:	Wednesday, July 26, 2000 10:42 PM
> To:	Arnold, Curt; xml-dev@x...
> Subject:	RE: Didier's lab report
> 
> Hi Curt,
> 
> Curt said:
> It should be possible for an XSLT implementation to use asynchronous
> retrieval of document() using variables.
> 
> Say, if you had something like this
> 
> <xsl:transform ....>
> 
> 	<xsl:variable name="doc1" select="document('doc1.xml',.)"/>
> 	<xsl:variable name="doc2" select="document('doc2.xml',.)"/>
> 	<xsl:variable name="doc3" select="document('doc3.xml',.)"/>
> 
> 
> 	<xsl:template match="/">
> 		<xsl:apply-templates/>
> 	</xsl:template>
> 
> 	...
> </xsl:transform>
> 
> The declaration of the variable could start the download/parsing process
> but
> not block further execution.  Only when the variable was used in an
> expression
> would the template evaluation thread need to block.
> 
> I do not know if any of the existing processors implement this type of
> behavior,
> however it would not seem to require any changes to XSLT to approach the
> performance that you estimated for XInclude.
> 
> Didier replies:
> If I understand you well, this would imply first that we are allowed to
> use
> as a variable an external document tree. Then, if the XSLT processor
> recognizes that the select is a document() function, that the XSLT
> processor
> starts a thread to set the variable to a tree (will take as much time as
> the
> external server will take to return the resulting document). After having
> started a thread, the XSLT engine would go to the next variable
> assignment.
> 
> Cheers
> Didier PH Martin
> ----------------------------------------------
> Email: martind@n...
> Conferences: xml devconf 2000 (http://www.xmldevconf2000.com)
> Book: XML Professional (http://www.wrox.com)
> column: Style Matters (http://www.xml.com)
> Products: http://www.netfolder.com

• Follow-Ups:
  • Re: Didier's lab report
    • From: mark hu <mark@f...>

• Prev by Date: RE: An other /%?/&*" patent - help requested from the community.
• Next by Date: RE: XML, MicroSoft, Torquemada and Comics (was RE: XML in .NET - morethan just SOAP?)
• Previous by thread: Re: Didier's lab report
• Next by thread: Re: Didier's lab report
• Index(es):
  • Date
  • Thread