James Bucanek <mailto:email@hidden> wrote (Thursday,
October 18, 2007 10:09 PM -0700):
It appears that NSSocketPort does not, however, destroy the
socket/pipe file once the NSSocketPort is invalidated. You'll have to
do this yourself. Currently, I'm adding code to catch the port's
NSPortDidBecomeInvalidNotification and delete the socket file.
I can now confirm that this is true. You must delete the socket
file created by NSSocketPort once you are done with the connection.
Also, [NSConnection invalidate'] does not (immediately)
invalidate the port, so it never fires the
NSPortDidBecomeInvalidNotification. At least not in my test
program, that terminates the instant it invalidates the
connection. To get that notification to fire, I had to call
[[connection receivePort] invalidate].
--
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
