Re: XSLT processor performance

Subject: Re: XSLT processor performance
From: Lars Marius Garshol <larsga@xxxxxxxxxxxxxxx>
Date: 28 Jul 2000 18:16:09 +0200
* Lars Marius Garshol
| 
| So the document, and Sablotron's treatment of it, are both legal.
| However, a good XSLT engine _should_ include external entities.

* Sebastian Rahtz
| 
| just to be clear, it was TransforMiiX, not Sablotron (and I though
| they both used Expat?)

Sorry, my bad.

I think TransforMiiX does use expat, but older versions of expat did
not include external entities. You can do it with newer versions, but
it requires implementing an extra callback on the part of the
application. So it's not enough to just set a flag or something, you
have to implement reading data from the entity and pushing it into
expat yourself.

Expat works this way because 
 
  a) it's been designed to be incremental, so that the application
     _has_ to push data to it

  b) this way expat is independent of the URL framework that is used
     in the application

--Lars M.


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


Current Thread