Client Data Field Synchronization with Dependency Disablement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In client-server architectures, synchronizing data between client and server while allowing changes in some client objects while prohibiting changes in dependent objects is challenging, leading to reduced utility and responsiveness of the interface.
Innovation Solution
A method where the client computer writes a new data value to a first data field, sends a refresh request to the server, receives a refresh response, and then enables writing to dependent data fields, ensuring that only data fields not dependent on the changed field can be modified during the refresh process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If changes to dependent client objects are prohibited to maintain data consistency, then data reliability is improved, but interface utility and responsiveness deteriorate
Solution Approach 1:
The patent segments the client objects into independent and dependent categories based on their data relationships. When a change is detected, only the affected dependent objects are disabled while independent objects remain editable. This selective segmentation maintains data consistency for critical paths while preserving interface responsiveness for non-critical operations.
Solution Approach 2:
The system dynamically adjusts the editability state of client objects based on real-time change detection and dependency analysis. The disabled state is temporarily applied only to dependent objects during the refresh operation, and automatically reverted afterward. This dynamic state management resolves the contradiction by making the restriction temporary and context-specific rather than permanent and universal.
2Reliability
If all client objects are disabled during refresh to prevent data loss, then data reliability is improved, but productivity deteriorates
Solution Approach 1:
Instead of disabling all client objects uniformly, the patent segments them based on their dependency relationships with the changing object. Only objects that are truly dependent on the changed data are disabled, while independent objects remain fully functional. This selective approach maintains data integrity for critical operations while preserving productivity through continued access to non-critical functions.
Solution Approach 2:
The disabled state is applied locally and specifically to only those client objects that have a direct dependency relationship with the changed object, rather than applying a global restriction. This localized quality control ensures data integrity where needed while maintaining interface utility and productivity in areas where data consistency is not affected.
3Ease of operation
If dependent data fields are enabled during refresh, then interface responsiveness is improved, but data errors increase
Solution Approach 1:
The patent applies preliminary anti-action by disabling dependent data fields before the refresh operation occurs. This preventive measure blocks potential data errors from occurring in the first place, rather than attempting to correct them afterward. The disabled state acts as a protective barrier that prevents users from entering conflicting data during the critical refresh window, thereby maintaining data accuracy while still allowing interface responsiveness through selective enabling of independent fields.
Data Source
AI summary
Methods for synchronizing data in client-server architectures are described. A client stores data in first and second fields. The value stored in the second field depends on the value stored in the first. When the client writes a new value to the first field, it disables writing to the second field. The client sends a refresh request and receives a refresh response from a server. The refresh request and response contain differences in data stored in the client and server fields. If the refresh response includes a new value for the second field, the client writes the value to the second field. A round trip pending flag associated with the first field is set. A data invalid flag associated with the second field is set. New data can be written to a third field when the value of the third field does not depend on the value of the first field.