Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
- Subject: Re: [Q] Why is the threading and UI updating designed to be done only on a main thread?
- From: Scott Ribe <email@hidden>
- Date: Wed, 14 Mar 2012 09:48:36 -0600
On Mar 14, 2012, at 9:21 AM, JongAm Park wrote:
> Of course. So, it is better to avoid such case, just like threading itself.
That's really not what I meant. I meant that if you're at the level that you design things such that the main thread and background worker threads deadlock, adding more UI threads would only allow you to make a worse mess in a flailing misguided attempt to solve the problem. Threads themselves are very useful; multiple threads taking user input and updating the display to the user are not really useful, and the request for them more often than not betrays a lack of understanding of threading.
--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice
_______________________________________________
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