Client-Library version 11.1 and later provide reentrant libraries that support thread-safe applications on most platforms. In some situations, Client-Library developers can use a multithreaded design to improve response time or throughput. For example:
An interactive Client-Library application can use one thread to query a server and another thread to manage the user interface. Such an application seems more responsive to the user because the user-interface thread is able to respond to user actions while the query thread is waiting for results.
An application that uses several connections to one or more servers can run each connection within a dedicated thread. While one thread is waiting for command results, the other threads can be processing received results or sending new commands. Such an approach may increase throughput because the application spends less idle time while waiting for results.
See the Client-Library chapter in the Open Client and Open Server Programmer’s Supplement for information on which system thread libraries, if any, can be linked with Client-Library on your platform.
See “Multithreaded Programming” in the Open Client Client-Library/C Reference Manual for information on coding Client-Library calls in a multithreaded application.
