FROM : ben syverson
DATE : Thu May 15 20:42:04 2008
Hi all,
I have a bit of a dilemma. I'm working on a Foundation-based command-
line utility that needs to manage a few threads. The obvious choice is
NSThread, since it's nice and clean.
Actually, I'm able to spawn new threads perfectly well. The problem is
that I can't (?) use performSelectorOnMainThread: because I'm not an
NSApplication, and so I don't get the default "main" thread that loops
for user input...
Am I busted? I would like to be able to run this app without the
window server running (ie, in Single User Mode), because it's server
software.
I can always fall back to POSIX threads, but I'd rather use NSThread
if possible. Is there an alternate way to have my spawned NSThreads
call back to a controller thread (that doesn't require 10.5)?
Thanks!
- ben
DATE : Thu May 15 20:42:04 2008
Hi all,
I have a bit of a dilemma. I'm working on a Foundation-based command-
line utility that needs to manage a few threads. The obvious choice is
NSThread, since it's nice and clean.
Actually, I'm able to spawn new threads perfectly well. The problem is
that I can't (?) use performSelectorOnMainThread: because I'm not an
NSApplication, and so I don't get the default "main" thread that loops
for user input...
Am I busted? I would like to be able to run this app without the
window server running (ie, in Single User Mode), because it's server
software.
I can always fall back to POSIX threads, but I'd rather use NSThread
if possible. Is there an alternate way to have my spawned NSThreads
call back to a controller thread (that doesn't require 10.5)?
Thanks!
- ben






Cocoa mail archive

