Open Client applications that use the session-free model are presumed to employ a threading model such that each request executes on a separate thread. This becomes particularly important in the following areas:
When the application constrains the size of the connection pool, requests can become blocked if connections are unavailable. This is accomplished by the Open Client Runtime blocking the thread on which the request is run.
Certain request-specific methods must be executed on the same thread on which the request was run. For more information, see Common methods.
A thread can only execute one request at a time. A thread that runs a request that returns output result sets may not run another request until all the result set data has been retrieved.
When the application constrains the size of the connection pool, requests can become blocked if connections are unavailable. This is accomplished by the Open Client Runtime blocking the thread on which the request is run.