Re: threads vs run-loops for keeping your GUI responsive
Re: threads vs run-loops for keeping your GUI responsive
- Subject: Re: threads vs run-loops for keeping your GUI responsive
- From: Shawn Erickson <email@hidden>
- Date: Fri, 9 Dec 2005 12:27:19 -0800
On 12/9/05, Markus Hitter <email@hidden> wrote:
>
>
Am 09.12.2005 um 19:26 schrieb Erik Buck:
>
>
> It is so hard in a multi-threaded process that in my opinion it is
>
> almost never justified to use multiple threads per process for most
>
> types of application.
>
>
Doesn't each Cocoa app come with three threads by default already?
Usually only one, two if the UI heartbeat thread is being used by the
framework, and sometimes more depending on what frameworks and
features you are using.
>
Having a working thread and a GUI thread is fine, IMHO, and fits
>
almost all of your discussion. In earlier days, you'd have used
>
signal handlers for this stuff.
Personally if you can spin it off to a separate process you can spin
it off into a thread inside of the same process. It really can be easy
to implement a multithread application as long as you don't make it
hard on yourself.
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden