Re: NSMessagePort Invalidation
Re: NSMessagePort Invalidation
- Subject: Re: NSMessagePort Invalidation
- From: Keary Suska <email@hidden>
- Date: Thu, 17 Jul 2008 08:48:21 -0600
- Thread-topic: NSMessagePort Invalidation
7/15/08 8:48 AM, also sprach email@hidden:
> 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?
Are you using Distributed Objects? If not, my recollection is that you
should be using NSMachPort instead. If you are using DO, I think Do is
supposed to handle those types of communication issues.
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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