which choice to implement iterations on separate threads
which choice to implement iterations on separate threads
- Subject: which choice to implement iterations on separate threads
- From: Jaime Magiera <email@hidden>
- Date: Mon, 25 Feb 2008 21:36:53 -0500
Hello,
I'm trying to get a sense of what folks are doing for applications
with individual threads for pulling samples at timed intervals,
updating UI, etc. Looking over the docs, the options are NSTImer,
NSThread and the new NSOperationQueue.
At a casual glance, NSOperationQueue doesn't have any scheduling.
There are a couple ways to ostensibly add it. Not ideal though.
NSTimer seems like a bad choice due to the dropping of an iteration if
the previous isn't completed. Not good if the called method takes a
little longer than expected (found this out the hard way).
This leads me in the direction of using an NSThread with either an
NSTimer in it or utilizing a while() with the new sleepForTimeInterval
or some other delay within.
Is this is a reasonable understanding of the situation for Cocoa? What
are folks generally using for timed actions on separate threads?
Jaime Magiera
Sensory Research
http://www.sensoryresearch.net
_______________________________________________
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