Persistent Web API Connection Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web API communication methods require opening and closing connections for each request, leading to high overhead and slow performance, which can deter users due to apparent slow communication and long load times.
Innovation Solution
Establishing a persistent connection between communication devices allows for multiple API requests to be handled without reopening the connection, reducing latency and improving response times by maintaining active connections and switching between them efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a connection is opened and closed for each web API request, then connection management is simple, but communication performance deteriorates due to high overhead and slow response times
Solution Approach 1:
The system establishes a persistent connection in advance before API requests are made. The connection is maintained open and ready for multiple requests, eliminating the need to repeatedly establish new connections. This preliminary action of pre-establishing the connection resolves the contradiction by reducing the time loss associated with connection establishment while maintaining simple connection management through a single initial connection setup.
Solution Approach 2:
The patent implements a persistent connection that remains open continuously across multiple API requests. Instead of repeatedly opening and closing connections, the useful action of data transmission continues over the same established connection. This continuity eliminates the repeated overhead of connection establishment and teardown, significantly improving API request handling speed while reducing the time lost to connection management operations.
2Productivity
If multiple procedures are executed on a persistent connection, then communication efficiency improves, but connection management complexity increases
Solution Approach 1:
The persistent connection is designed to handle multiple different procedures and API requests through a single universal interface. The same connection infrastructure supports various types of API calls and procedures, making the connection management system multi-functional. This universality allows multiple procedures to be executed efficiently over one connection without proportionally increasing management complexity, as the same connection handling logic serves multiple purposes.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of communication between devices is provided. The method comprises receiving a connection request, establishing a connection in response to the connection request, and receiving a first web API request on the connection. The method further comprises executing a first procedure in response to the first web API request, receiving a second web API request on the connection, and executing at least one of the first procedure or a second procedure in response to the second web API request.