Lihong,
Just an idea - try using xslt to split the document in n smaller documents.
Then if you need to relate adjacent children you can have child x-1 x x+1 in memory
and roll through them all but it sounds like you don't even require this.
>Hi,
>I'm trying to parse a large xml file (7MB) using
David,
It did look rediculous. However, there's some reason for it. We had a wrapper
subsystem on xerces-c. Recently we
upgrade the source code from version 1.3( very old one) to 2.2. 1.3 has a very
different memeory management
system from 2.2. Since we only expose DOM parser interface, we could
Hi,
This makes no sense. You cannot get the document until the parser is
finished parsing it, so there's no way to use the DOMParser for this.
Also, how can you say the DOM parser no longer needs a particular child?
It's building a DOM representation of the document and that means
everything
I dont think you can save memory by deleting child nodes as it will cause an exception
if you delete a child (implying it has a parent). Also, I dont see how it can save
memory even if you could delete the child nodes because the DOM document is going to
load the entire xml into memory atleast w
