HTTP Server Chunked Transfer Coding for Monitoring Status
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional HTTP server communication methods for monitoring objects, such as printer status, result in high communication overhead, increased process load, and status mismatches between the server and client due to frequent reconnection and transmission of full status reports.
Innovation Solution
An HTTP server that uses chunked transfer coding to transmit only differential status reports to the client when changes occur, with unique headers and footers added to the data, allowing continuous monitoring with reduced communication and process loads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the server returns a single status report and disconnects after each request, then the communication protocol is simple, but the communication overhead is large and process load increases
Solution Approach 1:
The server maintains a persistent connection with the client after the initial HTTP request, allowing continuous transmission of status update chunks without requiring repeated connection establishment and termination cycles. This continuous action eliminates the overhead of repeated handshakes while keeping the protocol framework simple.
Solution Approach 2:
The status report is divided into multiple chunks that are transmitted sequentially over the persistent connection. Each chunk represents a segment of the overall status information, allowing efficient transmission without requiring the client to request the entire status report repeatedly.
2Productivity
If the client cyclically requests status reports at constant intervals, then the client can periodically update the status, but mismatches occur between actual status and comprehended status due to transmission cycle delays
Solution Approach 1:
The server pushes status update chunks to the client as soon as status changes occur, providing immediate feedback rather than waiting for the next scheduled client request. This real-time feedback mechanism ensures the client comprehends status changes without delay, eliminating mismatches between actual and comprehended status.
Solution Approach 2:
The server prepares and transmits status update chunks proactively when changes occur, rather than waiting for the client to request them at fixed intervals. This preliminary action ensures status information is delivered immediately, preventing information loss during transmission cycles.
3Reliability
If the server transmits full status reports repeatedly, then the client receives complete status information, but the data volume is large and communication load increases
Solution Approach 1:
The server extracts and transmits only the changed portions of the status report as separate chunks, rather than transmitting the entire status report repeatedly. This extraction approach maintains information reliability for changed elements while significantly reducing the total data transmission volume.
Solution Approach 2:
The server transmits only the necessary partial information (changed status elements) rather than the complete status report. This partial action is sufficient to maintain client-side status accuracy while minimizing communication load and data volume.
Data Source
AI summary
An HTTP server including a communication section which communicates with a client, and a control section which, as a response to an HTTP request for requesting a report pertaining to a monitoring object received from the client via the communication section, transmits the report via the communication section to the client by making the report with chunked data in chunked transfer coding, upon a change of the monitoring object occurs.