Messaging API Over HTTP for Persistent Context
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing remote procedure call (RPC) protocols are complex and require specialized configurations, leading to server overload when multiple users access data, resulting in lost connections and the need for re-authentication upon reconnecting, which reduces user experience and prevents seamless data access.
Innovation Solution
A messaging-over-HTTP protocol is employed, where a client uses HTTP POST requests with specialized headers to retrieve data from a remote server, establishing a context through cookie generation and validation, allowing for persistent authentication and reduced re-authentication requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RPC protocol is used for data retrieval, then data can be accessed from remote server, but server becomes overloaded and connections are lost due to protocol complexity and redundancy
Solution Approach 1:
The patent introduces an HTTP-based messaging protocol as an intermediary between the client application and the remote server. This intermediary protocol simplifies the communication layer by using standard HTTP methods (POST, GET) with structured message formats, replacing the complex RPC protocol. The message structure includes standardized fields for requests and responses, reducing the complexity burden on the server and improving connection stability.
2Productivity
If RPC protocol requires specialized server configuration, then data retrieval is enabled, but multiple users cause server overload and connection loss
Solution Approach 1:
The patent segments the communication protocol into distinct, manageable components: HTTP request messages with specific headers, structured body content with defined fields, and standardized response formats. This segmentation allows the server to process each message component independently and efficiently, reducing the overhead burden when handling multiple concurrent user requests and preventing server overload.
3Ease of operation
If connection is lost in RPC protocol, then user must re-authenticate, but this reduces user experience and prevents seamless data access
Solution Approach 1:
The patent implements preliminary authentication where the client application establishes credentials and context with the server before actual data operations begin. The authenticated session context is maintained server-side and associated with the client's device identifier. If a connection is lost, the client can re-establish the connection using the same device identifier, and the server recognizes the pre-established authentication context, allowing the user to resume operations without re-authenticating, thus saving time and improving ease of operation.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Technologies are provided for a protocol for retrieving data from a remote server at a local client and establishing a context for the client at the server. A client may execute an application enabling users to receive data such as emails stored at the server. The client may employ a messaging-over hypertext transfer protocol (HTTP) to request the data from the server. An HTTP POST request may incorporate specialized headers with instructions for data retrieval, and may enable the client to establish a context with the server to identify the client for subsequent data requests. After receipt of the POST request, the server may send a receipt response and chunked intermediary responses while the request is being processed. The server may also send a cookie to the client representing the context of the client, and the client may return the cookies with subsequent data requests to the server.