Re: experts : is performSelectorOnMainThread blocking ?
Re: experts : is performSelectorOnMainThread blocking ?
- Subject: Re: experts : is performSelectorOnMainThread blocking ?
- From: Nathan Day <email@hidden>
- Date: Sun, 17 Nov 2002 16:44:53 +1030
I wrote a class to to a similar thing to performSelectorOnMainThread:
and if they do it anything like I have then they probable set up a
NSPort to the NSRunLoop to pass the messages to the main run loop. I
have found that the port can buffer a small number of messages (about 5
last time I checked) and then attempts to pass more messages will block.
On Saturday, November 16, 2002, at 10:45 PM, Benjamin Golinvaux wrote:
Hi
i would like to know if
performSelectorOnMainThread:withObject:waitUntilDone:
is a potentially blocking call, because i'd like to call it from a
real-time (CoreAudio
ioproc) thread and i want to avoid priority inversion. (I am passing
NO for the "wait"
parameter).
(if probably posts something somewhere in a queue, and i'd like to now
if this
queue supports non-blocking message posting, even in the worst case).
Thanks
Benjamin Golinvaux
Arboretum Systems, Inc.
www.arboretum.com
_______________________________________________
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.
Nathan Day
http://homepage.mac.com/nathan_day/
_______________________________________________
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.