• 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: [CFSocket] When should a CFSocketRef be invalidated?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [CFSocket] When should a CFSocketRef be invalidated?


  • Subject: Re: [CFSocket] When should a CFSocketRef be invalidated?
  • From: "Quinn \"The Eskimo!\"" <email@hidden>
  • Date: Thu, 13 Jan 2011 11:54:51 +0000

On 12 Jan 2011, at 20:05, Stéphane Sudre wrote:

> I have a process that uses CFSocketRef to connect to a TCP server and get some data.

In general we recommend that folks use CFStream (or NSStream) to manage TCP connections, rather than CFSocket.  CFSocket is mainly just about run loop integration, while CFStream adds byte stream semantics on top of that.  Thus CFSocket is useful where there's no byte stream (listening sockets, datagram sockets, other weird-arse sockets), but TCP connections are typically better handled by CFStream.

S+E
--
Quinn "The Eskimo!"                    <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >[CFSocket] When should a CFSocketRef be invalidated? (From: Stéphane Sudre <email@hidden>)

  • Prev by Date: Re: [CFSocket] When should a CFSocketRef be invalidated?
  • Next by Date: Re: [CFSocket] When should a CFSocketRef be invalidated?
  • Previous by thread: Re: [CFSocket] When should a CFSocketRef be invalidated?
  • Next by thread: Best practice for large packets
  • Index(es):
    • Date
    • Thread