Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

An approach to dynamically configuring http KeepAlive (Web servers, Application Servers)

IP.com Disclosure Number: IPCOM000236395D
Publication Date: 2014-Apr-24
Document File: 1 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

An approach to dynamically configure HTTPKeepAlive flag on web/application servers to achieve improved performance.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 68% of the total text.

Page 01 of 1

An approach to dynamically configuring http KeepAlive (Web servers, Application Servers)

The HTTPKeepAlive flag is used to improve performance of webservers and for faster rendering on UI in the browsers, but there are upsides/downsides of using this flag, as is evident by multiple conflicting articles on the web regarding this flag.

KeepAlive ON increases the performance on the client, but the server performance takes a hit (Thread based servers reserve a certain amount of memory for each live connection, which ultimately affects the performance of the server during heavy load).

KeepAlive OFF leads to degraded performance on the client.

The proposed solution here provides a ideal way of using this flag which leads to optimum performance on both the client and server.

The solution being proposed aims at solving the above problems by making the KeepAlive flag dynamic, using historical usage data and/or manual configuration by user. By dynamically setting this flag one can achieve optimal performance on the client as well as the server
Two ways to solve this problem:
1) User manually provides the setting of the flag based on URL/Header/Referrer attributes in a configuration file
2) The server can determine the value of the KeepAlive flag by using a combination of URL/Referrer/Header tags in the HTTP requests. After a certain amount of data has been collected for a webapp, the webserver can now start determining the usage patterns for the application and start setting...