On Thu, Nov 6, 2008 at 6:38 AM, Stefan Hafeneger <[EMAIL PROTECTED]> wrote: > I've checked it again. The class name is still the one of the original > object, but the class itself is NSDistributedObject. So it's exactly what I > wanted.
And in fact it must be. The same object cannot exist in two different processes, after all. It is possible to have objects copied across the connection rather than proxied. But this requires you to take explicit action to make it happen (you have to conform to NSCoding in a special way, as I remember it) and since you presumably didn't, that can't be happening. But the purpose of an NSDistantObject is to look as much like the real object as possible, so you have to examine it pretty closely to notice the difference. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
