• 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
Distributed Object Memory Management
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Distributed Object Memory Management


  • Subject: Distributed Object Memory Management
  • From: David McGavran <email@hidden>
  • Date: Tue, 2 May 2006 21:16:03 +0200

Docs are particularly weak on this subject.

I have a server that serves up something like

@protocol ServerProtocol
- (void)GetObject: (in bycopy const NSString*)objName OutObj:(out id*) outObj;
@end


On the server I implement that as so:

*outObj = [[SomeObj new] init];

And I let the client take ownership of the object. i.e. I don't have a pointer to it anymore only the client does.

So the retain count on the server side is 1. The client owns it. How does the client release it? I have tried different versions of release on the id returned but it never triggers the object's dealloc on the server side. Do I need to add a special release method to my protocol? Is there a good doc on Distributed Objects memory management?

Thanks

Dave
_______________________________________________
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


  • Prev by Date: binding a textfield value like a popup button
  • Next by Date: Re: Font Size Problem in NSTableView
  • Previous by thread: binding a textfield value like a popup button
  • Next by thread: InstantMessage.framework
  • Index(es):
    • Date
    • Thread