Re: Distributed Objects question
Re: Distributed Objects question
- Subject: Re: Distributed Objects question
- From: "Tom Harrington" <email@hidden>
- Date: Thu, 20 Jul 2006 16:12:42 -0600
On 7/20/06, Mike Kobb <email@hidden> wrote:
If this is covered someplace in Apple's docs, please point me there.
I've looked and looked.
I'm using Distributed Objects to communicate between two Cocoa apps.
It all seems to work very well. My "server" app vends an object by
registering an NSProtocolChecker with the default NSConnection, and
the client gets the object just fine.
Here's what I couldn't find in the documentation. Let's say that the
server needs to shut down. Is there some graceful way for it to do
so to ensure that connected clients know that it has gone away, and
can stop trying to use the object that was vended?
With the default NSConnection you can register for
NSConnectionDidDieNotification and take appropriate steps.
If you're using some other NSConnection (say one that uses an
NSSocketPort) then you're out of luck, and the best you can do is
catch exceptions when they happen.
--
Tom Harrington
email@hidden
AIM: atomicbird1
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden