Rosyna wrote on Monday, March 12, 2007:
>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.
Additional thread, sure. Nested run loops, sure. But separate run loops? Run loops that steal distributed object messages? I've yet to run across any framework that does this (and certainly none of the ones I'm using this tiny little background application), although I'd be happen to shown where I'm wrong.
>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.
--
James Bucanek
_______________________________________________
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
This email sent to email@hidden
