RE: [xsl] converting xsl-wd to xsl1, msxml script changes

Subject: RE: [xsl] converting xsl-wd to xsl1, msxml script changes
From: Woody <woody@xxxxxxxxxxxxxx>
Date: Thu, 13 Feb 2003 22:50:54 +0000
From: =?iso-8859-1?Q?=22Braum=FCller=2C_Hans=22?= <H.Braumueller@xxxxxxxxxxxx>

if i understand correctly, you convert a node-set to a string, because you believe it is faster, do some search and replace, and then reconvert the result back to a node-set, for further processing.

Thats what I do in that example yes. I think I will have to dig out another example as that muddies the problem I have. currently my major problem isn't speed, its access of a nodeset from an xsl transform in javascript.

This sounds absurd for my experience. Try to resolve your problems with pure xslt, now that msxml supports the standard xslt. You will see it is much more simple that making roundtrips to javascript.
The msxml3 and 4 stylesheet processors are much more faster than the older versions, which used xsl-wd language.

The problem is at some point I have to use javascript (or some script) to relay values to a controlling program, so I need to be able to get a node set in javascript.


XSL-List info and archive:

Current Thread