Function calls that are not thread safe

Your multithreaded application at times requires access to functions or system services that are not thread safe. There are few completely safe alternatives for calling these functions.

To illustrate the alternatives, consider the example of a program that calls API foo(). Because function foo() is listed as not being thread safe, you need to find a safe way to call it. Two common options are using a global mutual exclusion (mutex) or using a separate job to run the function that is not thread safe.

• Use global mutexes to run functions that are not threadsafe
  One alternative you should consider when you need to call a function that is not threadsafe is using a global mutual exclusion (mutex) to run these functions.
• Use separate jobs to run functions that are not threadsafe
  There are several threadsafe mechanisms to submit a new job to complete the processing you need.