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 (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]
