Designing for Threads

The HP OpenCall SS7 APIs (except the TimerLib) are Posix.1c Thread-Restricted level B. This means that the interface is not thread-safe, but that it can be used by any single “dedicated” thread of a multi-threaded application. Every other API that is Thread-Restricted Level B must be called from the application thread where HP OpenCall SS7 APIs are called. HP OpenCall SS7 APIs are not cancel-safe or async-cancel safe. See the OS user manuals for more information about Posix.1c threads.

The HP OpenCall SS7 APIs are not Async-Signal-Safe (that is, no HP OpenCall SS7 functions can be called from a Signal Handler execution context).

The HP OpenCall SS7 APIs are neither Cancel-Safe nor Async-Cancel-Safe (that is, if the thread that uses an HP OpenCall SS7 function is cancelled by another thread, the HP OpenCall SS7 context is not left in a consistent state).