Persistent HTTP client sessions

The number of requests that are sent to an HTTP server can help you determine when to use persistent HTTP client sessions.

If the number of requests that are sent to an HTTP server is small, for example, one request per minute, use non-persistent HTTP client sessions. The cost of establishing the HTTP client session is minimal. However, if the number of requests that are sent to an HTTP server is large, for example, 1000 requests per second, use persistent HTTP client sessions. By using persistent HTTP client sessions, you can minimize the cost of establishing and closing a connection for every HTTP client request that was sent.

The tpf_httpSendRequest and tpf_httpSendAsyncRequest functions are used for both persistent and non-persistent sessions. Regardless of whether the request is processed across a persistent or non-persistent session, a system administrator can switch between session types without any application changes.