>> Since UDSs are bidirectional, I don't need an explicit receivePort. The
>> documentation for NSConnection states that if receivePort is nil, then a
>> port of the same type as sendPort will be automatically created. My guess is
>> that this is done to provide support for distributed objects over
On Fri, Feb 6, 2009 at 9:58 AM, Tim Murison wrote:
> My client application communicates with the server using Unix Domain
> Sockets. After creating a properly configured NSSocketPort (sendPort) for
> the client, I create the NSConnection as follows:
You're going to need to post the code you use t
Hi,
I've been working with distributed objects for the last few days and came
across a behaviour in NSConnection that seems to be a bug, or at least
sub-optimal.
My client application communicates with the server using Unix Domain
Sockets. After creating a properly configured NSSocketPort (sendPo
