Re: NSSocketPort initRemoteWithTCPPort is never valid
Re: NSSocketPort initRemoteWithTCPPort is never valid
- Subject: Re: NSSocketPort initRemoteWithTCPPort is never valid
- From: Ken Thomases <email@hidden>
- Date: Wed, 15 Jul 2009 13:19:47 -0500
On Jul 15, 2009, at 11:49 AM, Kirk Kerekes wrote:
An NSSocketPort is intended for use with Distributed Objects and
NSConnection or, at least, to communicate with another NSSocketPort
at
the other end.
The documentation used to state this, possibly erroneously. It no
longer does so:
"NSSocketPort is a subclass of NSPort that represents a BSD socket.
An NSSocketPort object can be used as an endpoint for distributed
object connections"
NSSocketPort is quite usable as an abstraction of a BSD socket. I
have written code that communicates with Winsock sockets using
NSSocketPort.
How did you force it to connect? What methods did you use to send and
receive data? Or did you just pluck out the socket fd and use that?
Regards,
Ken
_______________________________________________
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