/
Improving Response Times using HTTP Keep-Alive

Improving Response Times using HTTP Keep-Alive

This article pertains to: Legacy API (V1) Inform (v2)

To improve API call response times, HTTP has a feature called "Keep-Alive". These are connections that allow your application to hold a TCP connection open between your application and Validic servers once an API call has completed. When your application needs to send another API call, it can use this idle "Keep-Alive" connection rather than creating a new TCP connection. This eliminates the need to create a new connection thereby saving the time and resources needed to create it. This will improve Validic's average response times for your application at large.

To enable HTTP Keep-Alive for your application, you may check this resource on how to enable it for your application http://www.feedthebot.com/pagespeed/keep-alive.html. There are also many other resources on the web regarding how to enable the use of HTTP Keep-Alive connections specific to your application.

Related content

Common Oversights when Implementing Validic
Common Oversights when Implementing Validic
More like this
SSE Connection Best Practices
SSE Connection Best Practices
More like this
Managing Connections to a Stream
Managing Connections to a Stream
More like this
Best Practices to avoiding slow API response time
Best Practices to avoiding slow API response time
More like this
Streaming API vs Push Service
Streaming API vs Push Service
More like this
HTTP 422 Error when connecting to streams
HTTP 422 Error when connecting to streams
More like this