Re: Cocoa-dev Digest, Vol 4, Issue 999
Re: Cocoa-dev Digest, Vol 4, Issue 999
- Subject: Re: Cocoa-dev Digest, Vol 4, Issue 999
- From: David Spooner <email@hidden>
- Date: Wed, 10 Oct 2007 09:29:35 -0600
On Tue, 9 Oct 2007 18:06:17 -0400, "A.M."
<email@hidden> wrote:
Do you mean "bycopy"?
"Since passing by reference is the default behavior for the vast
majority of Objective-C objects, you will rarely, if ever, make use
of the byref keyword."
http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/
Articles/chapter_5_section_6.html
No, I mean byref.
The point is that if I have the server use NSArchiver to encode an
invocation, send the resulting data, and then use NSUnarchiver to
reconstruct the invocation on the client side, then I would have to
invest some effort to obtain NSDistantObjects corresponding to the
invocation's object arguments on the client side.
All that information is crammed into the method's signature. It has a
bunch of private methods you may be interested in.
I realize that I can parse an invocation's method signature to encode
and decode the invocation, but doing so would require significant
effort (to accommodate non-object arguments) and would presumably
replicate what has already been done for NSPortCoder. Thus my
original interest in whether it is possible to tweak NSPortCoder and/
or NSSocketPort to use a socket configured for multicast...
Cheers,
M
Best regards,
dave
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden