[Home] [By Thread] [By Date] [Recent Entries]
Michael Kay writes: [excellent observations snipped] > It's quite true, of course, that if you have enough memory to hold a DOM > representation of your document, then using SAX merely in order to save > memory is fairly pointless. But that doesn't seem a very profound > observation. A few years ago, when I was still profiling these things, Java-based DOM implementations were relatively slow to start up with large documents, even when the the documents fit in memory easily. Perhaps Michael and other DOM implementors have found ways to work around the problem, or Java VMs have gotten faster at allocating new objects. I've been messing around with something even closer to the metal (and more efficient) than SAX, just for fun. If anything comes of it, I'll post and let everyone know. All the best, David -- David Megginson, david@m..., http://www.megginson.com/
|

Cart



