Hi Matt,
because XT requires Java this actually made the whole process slower in our
testing. C didn't require having processes sporned all the time and also
allowed for concurrent processes, while for XT, each transformation required
closing java and re-opening it.
Thank you for you for your comments re arg:
I don't know much about this, although I just looked at the Sablotron
documentation and found ...
6.4 Named buffers
Sablotron introduces an URI scheme 'arg:' which enables one to use strings
in named memory buffers. The buffer names can have a tree-like structure so
that a relative reference from a document in a buffer can be resolved as
pointing to another buffer.
For instance, if we invoke Sablotron specifying that a buffer named /mybuf/1
contains the string "<a>contents</a>", then the expression
document('arg:/mybuf/1')/a
has string-value "contents". If the document in arg:/mybuf/1 contained a
relative URI reference "../theirbuf/2" then this would be resolved as
pointing to "arg:/theirbuf/2".
Is there any other documentation that I could be pointed to.
Thanks in advance
Tim
-----Original Message-----
From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 13 March 2001 10:30 AM
To: Sablotron Mailing List
Subject: RE: [Sab] xsl:include
On Tue, 13 Mar 2001, Tim Watts wrote:
>
> Previously we have been doing this successfully using XT and also Xalan,
but
> have moved to Sabletron to take advantage of the significant speed gains
> involved in a C++ parser
?? XT is faster than Sablotron according to the XSLTMark results...
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
