Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: NSSocketPort initRemoteWithTCPPort is never valid

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSSocketPort initRemoteWithTCPPort is never valid

Subject: Re: NSSocketPort initRemoteWithTCPPort is never valid
From: Kirk Kerekes <email@hidden>
Date: Wed, 15 Jul 2009 11:49:15 -0500

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.


_______________________________________________

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


Follow-Ups:

Re: NSSocketPort initRemoteWithTCPPort  is never valid
From: Ken Thomases <email@hidden>


Prev by Date:
Re: testing your app on a virtual machine?

Next by Date:
QuickLook

Previous by thread:
Re: NSSocketPort initRemoteWithTCPPort  is never valid

Next by thread:
Re: NSSocketPort initRemoteWithTCPPort  is never valid

Index(es):

Date
Thread