Document State Tracking via Request Identifier Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Web-based document editing systems face issues with data loss and inconsistency due to the need for all modification requests to be received in order by the remote server, leading to incomplete document updates if any request is missed or received out of sequence.
Innovation Solution
Implementing a state tracking module that transmits identifiers representing groups of modification requests instead of individual requests, reducing data transmission size and allowing for efficient recovery of document state in case of failures, by storing and referencing these identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all modification requests are transmitted individually between client and server, then complete document updates can be achieved, but data transmission size becomes large and recovery becomes difficult if requests are lost
Solution Approach 1:
The patent creates a simplified copy of the modification history by transmitting only identifiers (pointers) rather than complete request data. The server maintains a full copy of the modification history locally, allowing the client to reference it using small identifier tokens. This resolves the contradiction by enabling complete document updates through identifier references while minimizing transmitted data size.
Solution Approach 2:
The patent introduces an intermediary mechanism where the server acts as a mediator that stores the complete modification history and provides identifier references to clients. Instead of clients transmitting full request data, they exchange compact identifiers that the server resolves against its stored history. This intermediary approach enables reliable document updates with minimal data transmission.
2Loss of information
If individual modification requests are transmitted, then detailed tracking is possible, but the complexity of managing request sequences and recoveries increases
Solution Approach 1:
The patent segments the modification tracking system into two parts: the client holds compact identifier tokens representing modification groups, while the server maintains the detailed modification history. This segmentation allows detailed tracking to be performed by the server using stored identifiers, while the client manages only simple identifier references, reducing overall system complexity.
Solution Approach 2:
The patent applies partial action by having the client transmit only sufficient information (identifiers) to reference modifications, rather than complete request data. The server performs the excessive action of maintaining the full modification history locally, allowing accurate tracking without requiring complex client-side request management.
3Reliability
If the server stores complete modification history, then document state recovery is possible, but memory usage increases
Solution Approach 1:
The patent creates a compact copy mechanism where the server stores modification history with efficient identifier references. Instead of duplicating full document states, the server maintains a streamlined history using pointers and identifiers that reference modification groups. This enables state recovery while minimizing memory consumption through efficient data representation.
Data Source
AI summary
In an embodiment, a method is provided for tracking a state of a document that is accessible over a computer network. In this method, requests to modify the document are received by way of the computer network. A size of a set of these requests are identified to exceed a threshold size and an identifier that identifies this set of requests is generated. The identifier is then transmitted in a response to the requests by way of the computer network.