On Mar 1, 2008, at 5:44 PM, Kyle Sluder wrote:
On Sat, Mar 1, 2008 at 7:07 PM, Adam R. Maxwell <[EMAIL PROTECTED]>
wrote:
Does this apply to NSMachPort as well? I filed a doc bug hoping for
eventual clarification, but I'd rather know sooner rather than later
if the code has to be rewritten. rdar://problem/5772256
You're misinterpreting "thread-safe"; you can't send messages to an
NSPort on thread A from thread B. Since each thread is only
manipulating its own NSPort, you're in the clear.
Thanks, but I think you're misinterpreting the example :). The object
has a single NSMachPort ivar, added to the some thread's runloop.
When a notification arrives on a different thread in
processNotification:, it messages the NSMachPort. When the port's
delegate receives handleMachMessage: it processes the notification
since it's guaranteed to be on the correct thread.
--
adam
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
