[xsl] forwarded message from owner-xsl-list@mulberrytech.com

Subject: [xsl] forwarded message from owner-xsl-list@mulberrytech.com
From: Tony Graham <tkg@xxxxxxxxxxxx> (by way of B. Tommie Usdin)
Date: Thu, 11 Jan 2001 14:14:22 -0500
From graham.ellis@xxxxxxxxxxx Mon Jan 8 10:53:16 2001
Received: from syn2gw1.synopsys.ltd.uk (syn2gw1.synopsys.ltd.uk [])
by web3-1.ability.net (8.9.3/8.9.1/Pub) with ESMTP id KAA19471
for <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>; Mon, 8 Jan 2001 10:53:16 -0500 (EST)
Received: from syn1mx2.synopsys.ltd.uk (unverified) by syn2gw1.synopsys.ltd.uk
(Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000780456@xxxxxxxxxxxxxxxxxxxxxxx> for <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>;
Mon, 08 Jan 2001 15:56:20 +0000
Received: by syn1mx2 with Internet Mail Service (5.5.2650.10)
id <CHB9MRXT>; Mon, 8 Jan 2001 15:56:48 -0000
Message-Id: <C02FE75A852BD211820A00A0C944C9AC01AEF5AE@syn1mx2>
From: "Ellis, Graham" <graham.ellis@xxxxxxxxxxx>
To: "'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'" <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [xsl] XSLT or DOM or SAX?
Date: Mon, 8 Jan 2001 15:56:47 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain

I'm currently working on transforming small xml files, but at a high
frequency - (up to thousands per hour). Any suggestions as to what method
would be best for this scenario?

Graham Ellis
ACT Financial Systems

*	Tel:       +44 (0) 20 7250 1990
*	Fax:      +44 (0) 20 7553 4713
*	Email:  graham.ellis@xxxxxxxxxxx
*	http://www.actfs.co.uk

 From: 	David Halsted[SMTP:halstedd@xxxxxxxxxx]
 Reply To: 	xsl-list@xxxxxxxxxxxxxxxxxxxxxx
 Sent: 	04 January 2001 21:52
 To: 	xsl-list@xxxxxxxxxxxxxxxxxxxxxx
 Subject: 	Re: [xsl] XSLT or DOM or SAX?

 Yes, in general XSLT makes things easy that are more difficult in DOM or
 (or at least take more code), but at a performance cost.  SAX is great,
 though, if you are concerned about performance in handling large
 For what it matters, I tend to use XSLT when I know that the XML involved
 will be small because it makes things so easy, DOM when I need persistent
 structures (and have some sense for the size of the files involved), and
 when I'm running through files that may be large, like XML-ized versions
 data from large databases.  If you are looking for functionality you can't
 find in XSLT, you have the option of extending it.

Dave Halsted

 ----- Original Message -----
 From: James Robertson <jamesr@xxxxxxxxxxxxxx>
 To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
 Sent: Thursday, January 04, 2001 5:13 PM
 Subject: Re: [xsl] XSLT or DOM or SAX?

> At 07:50 3/01/2001, Craig Pfeifer wrote: > > >I wanted to know how you knew if/when you have reached the limits of XSLT, > >and it's time to look at a DOM / SAX solution? What sorts of > >transformations are too difficult/awkward to accomplish in XSLT and are > >better left to DOM / SAX implementations? > > DOM/SAX seems a pretty low-level alternative > to XSLT. > > You might want to have a look at Omnimark > instead for more complex transformations. > > J > > ------------------------- > James Robertson > Step Two Designs Pty Ltd > SGML, XML & HTML Consultancy > Illumination: an out-of-the-box Intranet solution > > http://www.steptwo.com.au/ > jamesr@xxxxxxxxxxxxxx > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list >

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

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

Current Thread