Skip navigation.
 
mlRe: Blocking loops
FROM : Bill Bumgarner
DATE : Fri Jun 16 20:11:55 2006

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

Related mailsAuthorDate
mlBlocking loops cocoa Jun 16, 15:24
mlRe: Blocking loops Shawn Erickson Jun 16, 16:20
mlRe: Blocking loops Andreas Känner Jun 16, 16:34
mlRe: Blocking loops Nicko van Someren Jun 16, 16:41
mlRe: Blocking loops A.M. Jun 16, 17:19
mlRe: Blocking loops Bill Bumgarner Jun 16, 18:05
mlRe: Blocking loops Bill Bumgarner Jun 16, 19:27
mlRe: Blocking loops A.M. Jun 16, 19:59
mlRe: Blocking loops Bill Bumgarner Jun 16, 20:11
mlRe: Blocking loops Drarok Ithaqua Jun 16, 21:47
mlRe: Blocking loops Shawn Erickson Jun 16, 21:53
mlRe: Blocking loops Michael Ash Jun 17, 17:31
mlRe: Blocking loops Agent M Jun 17, 20:53
mlRe: Blocking loops Bill Bumgarner Jun 19, 23:06
mlRe: Blocking loops Michael Ash Jun 21, 00:58