• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [Q] Remote Messaging : Keep sending msg to a destroyed remote object
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Q] Remote Messaging : Keep sending msg to a destroyed remote object


  • Subject: Re: [Q] Remote Messaging : Keep sending msg to a destroyed remote object
  • From: JongAm Park <email@hidden>
  • Date: Thu, 30 Aug 2007 19:42:57 -0700

Thank you very much for your comment.

I checked it but it didn't seem to have such an object which hold the remote object/proxy object.
One thing I guess is that it is held in a cache.


Can it be a good idea to file this as a bug?
At least the document is misleading as you mentioned that registerName: doesn't unregister what it registered.


Thank you.


Lukhnos D. Liu wrote:
On Aug 29, 2007, at 11:41 PM, JongAm Park wrote:
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

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >[Q] Remote Messaging : Keep sending msg to a destroyed remote object (From: JongAm Park <email@hidden>)
 >Re: [Q] Remote Messaging : Keep sending msg to a destroyed remote object (From: "Lukhnos D. Liu" <email@hidden>)

  • Prev by Date: Re: Line Numbers in Tables
  • Next by Date: Re: Who Calls Accessors in Bookmarks?
  • Previous by thread: Re: [Q] Remote Messaging : Keep sending msg to a destroyed remote object
  • Next by thread: Core Data / Bindings problem
  • Index(es):
    • Date
    • Thread