Problems with DO
Problems with DO
- Subject: Problems with DO
- From: Matt Massicotte <email@hidden>
- Date: Mon, 23 Dec 2002 16:09:46 -0500
Hi everyone,
Put a question up to the list about a month ago concerning some strange
behaviour with DO. My original problem was that if I passed an
NSString or NSNumber, or an NSArray of those objects, everything
worked, but my own objects didn't survive the trip across the network.
Someone replied, saying that they had a similar problem, and that
explicitly using NSArchiver and NSUnarchiver solved their problem. I
tried, and it worked for me too. I find this puzzling because DO's
documentation gave me the impression that this was automatically done.
Anyways...
Now, my problem is that a method that returns (bycopy id) is returning
objects that respond YES to [obj isProxy]. What am I missing here? I
thought that bycopy will produce a copy of the object in the calling
processes space. I am sure that I'm somehow implementing things wrong,
but I can't find a problem. Has anyone else see anything like this?
Matt Massicotte
email@hidden
_______________________________________________
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.