1

I have two options in front of me for parsing really fat XML file,

  • TouchXML
  • GDataXML

It's lot of work to do because XML file is very huge. I thought of asking people who have already worked with these parsers.

  1. Which one is better for fat XML files?
  2. I found a blog post which says that TouchXML does not edit/save XML files whereas GDataXML has that feature. What exactly do they mean by edit/save XML file feature?
jscs
  • 63,694
  • 13
  • 151
  • 195
TeaCupApp
  • 11,316
  • 18
  • 70
  • 150
  • I've used `GDataXML` before, and I'd have to say the performance was lacking. I've since switched to using `libxml2` itself (in a Cocoa wrapper [here](http://cocoawithlove.com/2008/10/using-libxml2-for-parsing-and-xpath.html)). Configuring the parser is a little more work, but the speed & memory usage improvements are definitely worth it in my opinion. – sudo rm -rf Dec 20 '11 at 06:09

1 Answers1

1

Lets see if I can answer your questions:

  1. Which one is better for fat XML files? The answer is neither. Both are DOM parsers, which actually load the entire document into memory to make queries faster. If you're parsing a large file, you're better off going with a SAX parser, such as the built-in NSXMLParser, or even the SAX-based version of libxml2.
  2. What exactly do they mean by edit/save XML file feature? Well, suppose you have a XML file that has your app's settings in it. If you open up that file and make changes, you're going to want to save them, right? That's where the writing comes in. The parsers that allow writing let you save the representation of the xml file in the memory into an actual file that can be written to disk.
sudo rm -rf
  • 29,408
  • 19
  • 102
  • 161