Re: Efficient XML loading [continuation of NSString from mapped NSData thread]

FROM : Louis Gerbarg
DATE : Wed May 14 20:13:55 2008

NSXMLParser needs to load everything into ram first, then it starts
generating its stream of events. I recommend filing a bug asking for
it to be enhanced to support incrementally available data. It will
definitely be a dupe (I've filed it, among others I am sure)., but the
more people who ask for it, the more likely it will get engineering
resources.

For situations where you have slow connections, high latency, large
documents, and/or limited ram being able to work with the file as a
stream is definitely a competitive advantage. While I (and a lot of
other people, I am certain) have written libxml2 interfaces to achieve
that, I would much rather just use NSXMLParser in the future.

Louis

On Wed, May 14, 2008 at 11:04 AM, Jens Alfke <<email_removed>> wrote:

> I am nearly always cheerfully willing to give out source code, but in this
> case I kind of see this as a competitive advantage for a product I might
> release in the future, so I'm going to keep the code to myself. It isn't
> brain surgery, or even rocket science, but it took some work; libxml2 is a
> lot lower-level than the plist API. (I didn't try using NSXMLParser, which
> is an Obj-C wrapper around libxml2; that might get you comparable
> performance with less pain.)
>
> —Jens
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
>