Re: Problems with Distributed Objects
Re: Problems with Distributed Objects
- Subject: Re: Problems with Distributed Objects
- From: Andreas Mayer <email@hidden>
- Date: Thu, 26 Feb 2004 16:39:41 +0100
Am 26.02.2004 um 15:44 schrieb Philippe Mougin:
Have you implemented the replacementObjectForPortCoder: method as
described at
http://developer.apple.com/documentation/Cocoa/Conceptual/DistrObjects/
index.html ?
No.
I don't want to "allow an object to encode itself as an instance of
another class or to replace another object for itself". So how would
that help?
Although I _did_ read the pages you suggested, I still don't know what
I'm doing wrong. I'm not even sure how bycopy is supposed to work. I
*think* the NSPortCoder, that is automatically created by the
NSConnection should invoke encodeWithCoder: on the object in question.
But that does not seem to be what happens ... also - what if the class
does not comply with the NSCoding protocol? Shouldn't that throw an
exception? Can't find anything about it in the documentation.
Andreas
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.