how dare you use the words 'visual basic' in this newsgroup. real XML
programmers always use java ;-))
AFAIK all existing XSLT processors use DOM (even the java ones). Because
XSLT allows you to jump all over the document, I think it would be very
difficut to produce one that didn't read the whole document in.
if your transformation is simple, I would suggest not using XSLT for it -
write a sax-based progam that processes it as a stream. (not sure if you can
do this with MSXML)
If you need to jump all over the document to get different parts, I think
you should probably re-atchitect the application to use a XML database or
lots of small pieces of XML held in flat files or RDBMS.
"CK" <ck*****@hotmail.com> wrote in message
news:44**************************@posting.google.c om...
Hello,
I have the 60 MB XML string and I am coding a program in Visual Basic
to run a XSL transformation on it. Currently, I'm using the Microsoft
standard MSXML 2.0 to create a DOM document, load the XML, and then
run the XSL transformation on it using the MSXML2.IXSLProcessor
interface.
The problem is that it kills my system because of an incredible amount
of memory that it requires to do this (around 850 MB). Are there any
other transformation methods that I can use in Visual Basic that will
take less memory then DOM?
Or perhaps some other method of transformation that uses SAX as input
rather than a DOM object ?
BTW, can't use .Net
ANy other ideas are appreciated...