• 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: CFHTTPMessage and thread safety
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CFHTTPMessage and thread safety


  • Subject: Re: CFHTTPMessage and thread safety
  • From: Quinn <email@hidden>
  • Date: Fri, 29 Aug 2008 12:05:02 +0100

At 16:48 +0100 28/8/08, Mark Thomas wrote:
Was wondering if anybody could advise on how thread safe the CFHTTPMessage
/ CFReadStream API's where ? (I am aware that I can use a runloop call
function, but I'm working on keep the main thread to a minimum)

Most modern APIs are thread safe at least on a per-thread basis. That is, if you run your entire HTTP messaging engine on a secondary thread, you won't run into problems. Passing objects between threads, and accessing the same object from multiple threads, is more likely to cause you problems.


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: 
 >CFHTTPMessage and thread safety (From: Mark Thomas <email@hidden>)

  • Prev by Date: Why might CFReadStreamCopyProperty(stream, kCFStreamPropertySocketNativeHandle) return NULL?
  • Next by Date: Re: How to change the system proxy configuration ?
  • Previous by thread: CFHTTPMessage and thread safety
  • Next by thread: Re: CFHTTPMessage and thread safety
  • Index(es):
    • Date
    • Thread