On Sep 30, 2009, at 5:03 AM, Ken Thomases wrote:
However, exactly because it's so tricky, the Cocoa frameworks are
not going to just arbitrarily invoke your code on some random thread.
Yup. Generally, the only time your code will run on a secondary thread
is if
— You create an NSThread
— You call -performSelectorOnBackgroundThread:
— You use an NSOperationQueue to schedule concurrent NSOperations
— You use the new Grand Central Dispatch features in 10.6
Otherwise the main thread's runloop is going to cooperatively schedule
all of the user events, timers, notifications and asynchronous
delegate callbacks.
—Jens_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
