hmmm not sure
DOM (aka xml document, xml data document)
this gives you a random access object that you can fully traverse
fast but 'expensive'
SAX (aka ? )
gives a foward only stream of xml which fires off events
(i only ever played around with this a bit in msxml)
e.g. series of events such as
elementfound,attribute found,attribute found, end of element found
you then needed to (in msxml at least)
implement an interface for each of these events that could be fired,
which in my example ended up as a big event handler with a massive case
statement
i'm not sure this helps you
i'm not even sure why you are trying to process such a huge xml doc in this
manner
why are you trying to do it out of interest?
"Sean Hoffman" wrote:
Something like this?:
XmlReader m_oXMReader = new XmlTextReader("Page.xml");
XslTransform m_oXSLTransform = new XslTransform();
m_oXSLTransform.Load("\default.xsl");
XPathDocument m_oXMLDocument = new XPathDocument(m_oXMReader);
XsltArgumentList xslArg = new XsltArgumentList();
m_oXSLTransform.Transform(m_oXMLDocument ,xslArg,
context.Response.OutputStream);
MACHINE IS ALREADY BIG AND FAST! :-)