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

Re: POSIX APIs and thread safety on OSX


  • Subject: Re: POSIX APIs and thread safety on OSX
  • From: Kevin Van Vechten <email@hidden>
  • Date: Thu, 02 Jul 2009 21:33:17 -0700

On Jul 2, 2009, at 3:09 PM, John Michael Zorko wrote:

I'm wondering how thread-safe POSIX calls like open(), connect(), read(), etc. are on OSX versions, specifically 10.3.9, 10.4.x, 10.5.x and 10.6.x?

These interfaces are thread-safe by most definitions. It is OK for multiple threads to be making these calls simultaneously. However, it is up to the application to ensure data integrity; using these calls with the same file descriptor on multiple threads simultaneously will yield unpredictable results.


Kevin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >POSIX APIs and thread safety on OSX (From: John Michael Zorko <email@hidden>)

  • Prev by Date: POSIX APIs and thread safety on OSX
  • Next by Date: Emulating Leopard launchd.plist behavior under Tiger
  • Previous by thread: POSIX APIs and thread safety on OSX
  • Next by thread: Emulating Leopard launchd.plist behavior under Tiger
  • Index(es):
    • Date
    • Thread