• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSXMLParser and initWithStream
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSXMLParser and initWithStream


  • Subject: Re: NSXMLParser and initWithStream
  • From: Fritz Anderson <email@hidden>
  • Date: Thu, 31 May 2012 09:58:02 -0500

On 31 May 2012, at 1:14 AM, John Drake wrote:

> I figured out what the problem was and answering it here incase anyone else runs into this problem in the future since +[NSXMLParser initWithStream] doesn't have a lot lot of documentation out there. I needed to call -[NSXMLParser parse] right after I allocate NSXMLParser and set myself as delegate. But because it's a synchronous function, I need to call it another thread so I don't block the current thread and it can receive the NSStream events.

Wow.

That's really surprising, given that Apple is acutely aware that synchrony on the main thread is evil. Is stream support in NSXMLParser intended only for files?

	— F


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


References: 
 >NSXMLParser and initWithStream (From: John Drake <email@hidden>)
 >RE: NSXMLParser and initWithStream (From: John Drake <email@hidden>)

  • Prev by Date: Re: Managed Objects and Contexts
  • Next by Date: GC and malloc question
  • Previous by thread: RE: NSXMLParser and initWithStream
  • Next by thread: CoreData, automatic migration and sandbox problems.
  • Index(es):
    • Date
    • Thread