• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSMessagePort Invalidation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSMessagePort Invalidation


  • Subject: NSMessagePort Invalidation
  • From: Ryan Brown <email@hidden>
  • Date: Tue, 15 Jul 2008 07:48:21 -0700

NSMessagePort doesn't seem to post the NSPortDidBecomeInvalidNotification notification when the remote port dies. It doesn't seem to matter if the remote port is closed via the invalidate method or by killing the process. The only way I am seeing the notification posted is when I send invalidate to the port locally.

This seems contrary to the documentation:

"Posted from the invalidate method, which is invoked when the NSPort is deallocated or when it notices that its communication channel has been damaged."

Is this a legit bug or have I missed something?

Ryan
_______________________________________________

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


  • Follow-Ups:
    • Re: NSMessagePort Invalidation
      • From: Keary Suska <email@hidden>
  • Prev by Date: iPhone: Implementing search and index combo, like Contacts?
  • Next by Date: Re: iPhone: Implementing search and index combo, like Contacts?
  • Previous by thread: Re: iPhone: Implementing search and index combo, like Contacts?
  • Next by thread: Re: NSMessagePort Invalidation
  • Index(es):
    • Date
    • Thread