NSConnection and independant queuing
NSConnection and independant queuing
- Subject: NSConnection and independant queuing
- From: Florent Pillet <email@hidden>
- Date: Wed, 5 May 2004 01:44:04 +0200
I'm trying to determine whether NSConnection and distributed objects
are the appropriate architecture for the application I'm developing. I
need to run tasks in a thread, each task may be lengthy to complete.
The main thread wants send a number of messages to the worker thread
"oneway", without waiting for the messages to be actually consumed.
That is, I want to enqueue tasks in the worker thread's runLoop.
My question is: will this work? the NSConnection documentation doesn't
make it clear whether the "oneway" keyword requires the target thread's
runLoop to actually consume the message before coming back from the
message send operation, or if it is just enqueuing it in the target
thread's incoming messages list (if such a thing exists).
Any hint on that? I'd rather not have to manage my own message queue ;-)
--
Florent Pillet, Code Segment email@hidden
Developer tools and end-user products for Palm OS & Mac OS X
ICQ: 117292463
http://perso.wanadoo.fr/fpillet
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.