Re: multicasting and distributed objects
Re: multicasting and distributed objects
- Subject: Re: multicasting and distributed objects
- From: "A.M." <email@hidden>
- Date: Tue, 9 Oct 2007 18:06:17 -0400
On Oct 9, 2007, at 15:57 , David Spooner wrote:
On Tue, 9 Oct 2007 14:01:27 -0400, "A.M."
<email@hidden> wrote:
Take a look at Avis:
http://avis.sourceforge.net/
Thank you.
Reliable multicasting is a notoriously expensive problem. Even if you
send a one-way message, how do you know it was received and being
processed over UDP multicast?
The server which sends the messages doesn't care, but marks each
message with an index so that clients can detect missed messages
and request those messages be sent again...
What limitation does your prototype impose so that it can't handle
NSInvocations?
I thought I had observed that NSInvocation does not respond to -
encodeWithCoder:; I see now that that it does on 10.4. That still
leaves the problem of byref objects (which I don't currently need).
At this point my interest is largely academic...
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
All that information is crammed into the method's signature. It has a
bunch of private methods you may be interested in.
Cheers,
M
_______________________________________________
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