Re: Why is Leopard annoying my users?
Re: Why is Leopard annoying my users?
- Subject: Re: Why is Leopard annoying my users?
- From: James Bucanek <email@hidden>
- Date: Tue, 20 Nov 2007 11:06:34 -0700
Alastair Houghton <mailto:email@hidden> wrote
(Tuesday, November 20, 2007 9:12 AM -0000):
Could this (above) be the problem? The docs for NSConnection say:
"If receivePort is nil, the NSConnection object allocates and uses a
new port of the same class as sendPort."
It's just a guess, but I wonder if the issue might be that it's
allocating a TCP socket rather than a UNIX domain socket... after all,
it has no way to name a UNIX domain socket if it allocates a new
NSSocketPort.
I'm beginning to suspect that you're correct. I think
NSConnection is just creating a generic NSSocketPort, which
defaults to a randomly assigned TCP socket, for the return
communications path. I had assumed that it would simply have
used the pipe for both -- but maybe that's not even possible.
If that's the case, then one solution might be to create two
pipes and specify both the receive and send ports for the NSConnection.
I've got another thread on the MacNetworkProg list going that
might suggest that I can go back to using Mach ports and avoid
this whole mess.
--
James Bucanek
_______________________________________________
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