Wow; this was a really nice and dispassionate answer....
On Wed, 6 Mar 2002, Joseph Kesselman/CAM/Lotus wrote: > > Some insight into how to choose between these approaches: > http://www.w3.org/DOM/faq.html#SAXandDOM > > Remember that the DOM is only an API. There can be DOMs that load data on > demand, or that swap their contents out to disk... so the assumption that > the DOM is always going to consume more memory than a SAX approach depends > on the specific DOM implementation, and on how much of the data your SAX > solution would have to retain for reuse. Similar caveats apply to speed > issues; you can't say "DOM tree walking is kinda slow", you can only > discuss the performance of a specific DOM implementation -- and don't > forget to compare it fairly to walking the custom data structures you'd > have had to build in your SAX solution. > > The DOM isn't always the right answer. But be sure you understand the > tradeoffs in real-world code before you make that decision. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
