• 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
Using asynchronous APIs with NSOperation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Using asynchronous APIs with NSOperation


  • Subject: Using asynchronous APIs with NSOperation
  • From: Matt DeFoor <email@hidden>
  • Date: Thu, 24 Feb 2011 10:08:44 -0500

I have been doing research in preparing to switch from manual
threading to the usage of NSOperation. Because my operations will be
executing asynchronous APIs from the CoreServices framework, it
appears that I'd be better off using concurrent operations. What is
not clear to me is, if I provide a callback to an asynchronous API, on
which thread is the callback called?

Also, does anyone have experience using NSOperation with asynchronous
APIs that take a runloop and a runloop mode as parameters? From my
research, it is not clear to me how one would pass the required
runloop parameters in the concurrent operation's start: method.
Perhaps it is as simple as using the main thread's runloop, but that
doesn't seem right.

Thanks in advance,
Matt
_______________________________________________

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

  • Follow-Ups:
    • Re: Using asynchronous APIs with NSOperation
      • From: James Montgomerie <email@hidden>
  • Prev by Date: Re: dynamic binding in initializers
  • Next by Date: Re: dynamic binding in initializers
  • Previous by thread: NSRuler for nonlinear measurements
  • Next by thread: Re: Using asynchronous APIs with NSOperation
  • Index(es):
    • Date
    • Thread