"It is *possible* to use NSSocketPort
to create a socket which you then communicate with using other
techniques, but you can't use NSSocketPort directly to talk to a
non-Cocoa app."
While the documentation used to imply this, it did not appear to be
true then, and the documentation no longer asserts this. If it was
ever true, it is unclear when the transition from true to untrue
occurred, but it appears that it was untrue at least by Tiger. It does
appear to be one of the most enduring myths about the frameworks,
perhaps because it seemed so **wrong**.
The current documentation states:
"NSSocketPort is a subclass of NSPort that represents a BSD socket. An
NSSocketPort object can be used as an endpoint for distributed object
connections or raw messaging"
It is indeed possible, and easy, to use NSSocketPort to communicate
with non-Cocoa applications, in fact one can easily use it to interact
with sockets on other platforms. I have used it to communicate with
WINSOCK sockets.
Message: 10
Date: Thu, 4 Dec 2008 11:43:35 -0500
From: "Michael Ash" <[EMAIL PROTECTED]>
Subject: Re: Big picture relationships between NSConnection,
Yes. NSPort is part of the Distributed Objects system. It's possible
to use NSPort on its own, but you must use it to talk to another
process which also uses NSPort. It is *possible* to use NSSocketPort
to create a socket which you then communicate with using other
techniques, but you can't use NSSocketPort directly to talk to a
non-Cocoa app.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
