Re: Two-way connection with NSConnection
Re: Two-way connection with NSConnection
- Subject: Re: Two-way connection with NSConnection
- From: Stefan Hafeneger <email@hidden>
- Date: Thu, 06 Nov 2008 12:31:10 +0100
Hi,
Okay that's what I wanted to hear. But still the object class(name) on
the receiver (= server) side is not NSDistantObject but the original
one.
With best wishes, Stefan
Am 06.11.2008 um 12:24 schrieb Jean-Daniel Dupas:
Le 6 nov. 08 à 12:12, Stefan Hafeneger a écrit :
Hi,
I would like to set up a two way connection between processes using
NSConnection. I currently have solved this vending an object in
each process. Now someone proposed to send self as a parameter
using the rootProxy to the vendor. This works, but I doubt that
this is the best solutions. I prefer to have an instance of
NSDistributedObject on the other side as well. Unfortunately I
could not find a way to get an instance on the vendor side. Any
ideas?
With best wishes, Stefan
When you send self as parameter, it is transformed into an
NSDistantObject proxy on the receiver side (as all objects you send
byref, which is the default).
Of course, you should not send self directly, but instead an
NSProtocolChecker instance that encapsulate self.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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