Date: March 2, 2006 9:13:00 PM CEST
Subject: Re: Distributed Objects
Greetings all,One thing to be noted on NSDistantObjects. First, the successes I have had force marshalling and unmarshalling of objects using the archiving / unarchiving feature of Cocoa, and I discovered this fact on my own. In essence this has similar effect to converting to an NSData type, and then sending. The nice thing is that this effect becomes automatic and can be optimized.
In fact, the thing I posted to Dalton was:
This is a marshalling issue, and Objective C (Cocoa) tends to use Archiving and Unarchiving as means of archiving this distributed computing concept. Basically, any object needs to have few operations that are called when the object is called or returned. The object also must have operations to un-archive it when it appears in the distant machine. The archive is essentially an NSData type (byte array) representing your data structure.
I hope this information helps. The Cocoa book published by the Big Nerd Ranch has an excellent section (Chapter 8 and 9 I do believe) on the archiving objects in Objective-C. I can only presume that a Carbon representation would have a similar thing.
Since I use NSDistantObjects quite a bit in my research, I am scheduled to include an appendix section into my report for this semester. I can post it sooner if it is any help to anyone.
Later,
Dan Beatty
Ph.D. Student
Texas Tech University
On Mar 2, 2006, at 1:41 PM, Daniel Jalkut wrote:
h allows any *object* (not raw bytes) to be referred to remotely from the other application, taking care of the data transit transparently.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
