Note that there a MANY APIs in Mac OS X that spawn their own run
loops/threads. DiscRecording, the Cocoa heartbeat thread.
AppleScript, and countless others I can't remember. Future versions
of Mac OS X will have APIs which no doubt spawn even more threads and
even more run loops.
Especially if you are cocoa, you can count on having threads that
aren't yours running with their own runloops in the background.
Ack, at 3/9/07, James Bucanek said:
>From pervious experience, I know that distributed object messages
are sent to whatever run loop is waiting at the moment, even if
that's not the thread that registered the NSConnection. What I
suspect is happening is that the run loop inserted by the APE module
is trying to service the message, which ends up calling GUI code,
which isn't thread safe and shouldn't be executed on another thread.
Is there anyway to prevent DO messages from being sent to run loops
running in another thread? I really don't want to turn on
independent conversation queuing, as I have call backs that would
cause dead-lock issues.
--
Sincerely,
Rosyna Keller
Technical Support/Carbon troll/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
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
