Web Server Dummy HTTP Connection Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The frequent creation and closure of HTTP connections between a Web server and a Web application server result in significant overhead, especially when SSL encrypted communication is required, leading to increased load and reduced response speed in high-speed internet environments.
Innovation Solution
Implementing a method to manage HTTP connections by establishing and reusing connections through the exchange of dummy HTTP requests and responses at preset time intervals, allowing the Web server to continue existing connections beyond the initial keep-alive time, thereby reducing the overhead of constant connection creation and closure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the Web server creates and closes HTTP connections frequently for each client request, then connection management is simple, but overhead increases and response speed decreases
Solution Approach 1:
The patent applies preliminary action by establishing HTTP connections in advance before they are needed. The Web server proactively creates connections to the Web application server and maintains them idle for a period, so that when client requests arrive, the connections are already ready for immediate use, eliminating the need for frequent connection creation and closure
Solution Approach 2:
The patent implements continuity of useful action by maintaining HTTP connections in a persistent state rather than creating and closing them repeatedly. The Web server keeps connections alive and reusable across multiple client requests, ensuring continuous availability of communication channels without the overhead of repeated connection establishment and termination
2Productivity
If the Web server establishes persistent HTTP connections to reduce overhead, then response speed improves, but connection management complexity increases
Solution Approach 1:
The patent applies periodic action by implementing a survival check mechanism that periodically verifies the status of persistent HTTP connections. The Web server sends check requests at regular intervals to determine if connections are still valid, and only closes connections that fail the survival check, thereby simplifying management of persistent connections by automating their lifecycle based on periodic status verification
Solution Approach 2:
The patent implements self-service by enabling the connection management system to automatically monitor and clean up invalid connections without manual intervention. The survival check mechanism allows the system to self-diagnose connection status and self-correct by closing only those connections that are no longer viable, reducing the burden on operators while maintaining connection persistence
3Reliability
If the Web server uses SSL encrypted communication for secure data transmission, then security improves, but overhead increases due to frequent connection creation and closure
Solution Approach 1:
The patent applies preliminary action by establishing SSL-encrypted HTTP connections in advance before client requests arrive. The Web server proactively creates secure connections to the Web application server and maintains them idle, so that when encrypted communication is needed for client requests, the secure channel is already established and ready for immediate use, eliminating repeated SSL handshake overhead
Solution Approach 2:
The patent implements continuity of useful action by maintaining persistent SSL-encrypted HTTP connections across multiple client requests. The secure communication channel remains alive and reusable, ensuring continuous encrypted data transmission without the overhead of repeatedly establishing and terminating SSL connections, thereby improving response speed while maintaining security
Data Source
AI summary
A method for managing connections using a dummy HTTP, the method comprising: upon receiving an HTTP request from a client, establishing, by a Web server, a connection to a Web application server to transmit the HTTP request to the Web application server over the connection; transmitting, by the Web server, an HTTP response received from the Web application server to the client; and continuing, by the Web server, the connection by exchanging a dummy HTTP request and a dummy HTTP response with the Web application server when a count of a duration time of the connection reaches a preset survival check time.