Re: Blocking loops
Re: Blocking loops
- Subject: Re: Blocking loops
- From: Bill Bumgarner <email@hidden>
- Date: Fri, 16 Jun 2006 11:11:55 -0700
On Jun 16, 2006, at 10:59 AM, A.M. wrote:
....
I am just disappointed because I spent a lot of time implementing the
non-blocking protocol and I will have to throw it into another
thread- so
I could have used a blocking API anyway...
I can understand your frustration. In general, it is best to move
any kind of data processing into a ***single*** additional thread
(can't believe I'm saying that -- threads generally cause pain) and
leave the main event loop free to serve the needs of the user as
quickly as possible.
All is not lost.... the non-blocking protocol will likely yield
benefits in the long term as you now have the flexibility to handle
data from multiple sources or push other processing into that thread
without worrying about I/O blocking that processing.
b.bum
_______________________________________________
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