Re: Distributed Objects question
Re: Distributed Objects question
- Subject: Re: Distributed Objects question
- From: Mike Kobb <email@hidden>
- Date: Thu, 20 Jul 2006 18:04:26 -0700
Okay, I'm using the default connection in this case, so that's good
for the server side. On the client side, where I'm calling
NSConnection" rootProxyForConnectionWithRegisteredName:host: method,
would I also receive a notification if the server bails out from
under me?
And, a more-general question. Apple's developer documentation says
that one should not depend upon notifications for critical events,
because although every effort is made to deliver them, they're not
guaranteed. In practice, just how reliable are they?
Thanks much,
--Mike
On Jul 20, 2006, at 3:12 PM, Tom Harrington wrote:
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.
_______________________________________________
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