Especially if you are cocoa, you can count on having threads that
aren't yours running with their own runloops in the background.
I've never seen this. But again, I want to point out that there's a
significant difference between a nested run loop in the main thread
(modal dialogs and mouse drag routines do this all the time) and a
separate run loop in it's own thread.
Apple frameworks can and do spawn threads which use their own
runloop. Foundation's url loading classes are an example of this.
If any runloop on a secondary thread can "steal" DO messages and have
the code run in the context of the "wrong" thread, please show us a
sample app which demonstrates the problem.
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
