Skip navigation.
 
mlDistributed Objects question
FROM : Mike Kobb
DATE : Thu Jul 20 23:35:08 2006

Greetings,

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?

Right now, I just invalidate the connection that I opened, and have 
the client check for timeout exceptions and so forth.

If there's a good reference for DO programming, I'd love to know what 
it is.  Apple's docs were pretty good in terms of getting it all set 
up, but are typically pretty short on source samples and didn't 
really discuss this topic much at all.

Thanks!
--Mike

Related mailsAuthorDate
mlDistributed Objects question Mike Kobb Jul 20, 23:35
mlRe: Distributed Objects question Tom Harrington Jul 21, 00:12
mlRe: Distributed Objects question Mike Kobb Jul 21, 03:04
mlRe: Re: Distributed Objects question Tom Harrington Jul 21, 05:18
mlRe: Distributed Objects question Michael Ash Jul 21, 05:28
mlRe: Distributed Objects question Mike Kobb Jul 21, 19:37