So, the client code receive the notification well, and destroy its
local proxy.
Now, because there is no exposed remote object, pressing "Get Remote
Object" button on the client side should fail in obtaining the
server's exposed object. But it retrieves something. The address is
different from that obtained by the 1st trial.
And whatever message, i.e. the one which is defined in a protocol,
or the remote object can handle, you send to the remote object, the
remote object receives it successfully.
I haven't studied the remote object issues for a while, but as I
remember, last time I tried it, registerName: nevers really
unregisters the server, though the documentation says so. Perhaps it's
better to see if the vended server object is really released by your
release call, or if it's still retained by somebody else.
It's understandable that your client retrieves something after the
server object is supposed to die, as what the client retrieves is a
new proxy object that still points to the same vended server object.
d.
_______________________________________________
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
