• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Conversion of CFSocketCreateWithNative -> NSSocketPort
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Conversion of CFSocketCreateWithNative -> NSSocketPort


  • Subject: Re: Conversion of CFSocketCreateWithNative -> NSSocketPort
  • From: Andrew Farmer <email@hidden>
  • Date: Fri, 27 Nov 2009 11:01:16 -0800

On 27 Nov 2009, at 06:48, Michael Ash wrote:
> There's no Cocoa version of this, as far as I know. However,
> CFSocketCopyPeerAddress is just a wrapper around the POSIX function
> getpeername(), so you can just get the native socket from your
> NSSocketPort and then call that.

Or just keep using CFSocketCopyPeerAddress. Using CoreFoundation is not a crime - it's just as much a part of OS X as Cocoa is, and it's not going to be removed at any point in the foreseeable future._______________________________________________

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

References: 
 >Conversion of CFSocketCreateWithNative -> NSSocketPort (From: RenĂ© v Amerongen <email@hidden>)
 >Re: Conversion of CFSocketCreateWithNative -> NSSocketPort (From: Michael Ash <email@hidden>)

  • Prev by Date: Re: Custom Controls Where to start
  • Next by Date: Re: My try/catch block isn't catching exceptions on 10.6
  • Previous by thread: Re: Conversion of CFSocketCreateWithNative -> NSSocketPort
  • Next by thread: Mount afp volume
  • Index(es):
    • Date
    • Thread