Client-Server Messaging Mode Transition for Coherency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client-server systems face inefficiencies in messaging due to the need to choose between stateless mode, which minimizes messaging but may not always result in fewer messages, and stateful mode, which provides higher coherency but increases messaging, depending on the number of readers and writers accessing an object.
Innovation Solution
A client-server system that transitions between stateful and stateless modes based on defined use cases, determined by the number of readers and writers accessing an object, to optimize messaging efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If stateful mode is used to provide higher coherency, then coherency is improved, but messaging between clients and server increases
Solution Approach 1:
The patent applies dynamics by making the system's operational mode flexible rather than fixed. The server dynamically transitions between stateful and stateless modes based on real-time detection of use case patterns (number of readers and writers accessing an object). This allows the system to adapt its coherency mechanisms to actual workload conditions, using stateful mode only when necessary for multi-reader/writer scenarios while defaulting to stateless mode for simpler cases, thereby reducing unnecessary messaging while maintaining coherency where needed
2Quantity of substance
If stateless mode is used to minimize messaging, then messaging is reduced, but coherency may be compromised
Solution Approach 1:
The patent applies parameter changes by modifying the system's operational parameters (stateful vs. stateless mode) based on detected use case characteristics. The server analyzes the number of readers and writers accessing an object and changes the mode parameter accordingly. This allows the system to optimize messaging by using stateless mode for single-reader/single-writer scenarios while switching to stateful mode when multiple readers or writers are present, thus maintaining coherency without excessive messaging overhead
3Device complexity
If a fixed mode is used for all use cases, then system simplicity is maintained, but messaging efficiency is reduced
Solution Approach 1:
The patent resolves this contradiction by introducing dynamic mode selection driven by use case detection. The server monitors access patterns (number of readers and writers) and automatically transitions between stateful and stateless modes accordingly. This dynamic approach maintains messaging efficiency by avoiding unnecessary state management overhead in simple scenarios while ensuring coherency is maintained when multiple clients are accessing the object simultaneously
Data Source
AI summary
A detection that a client-server system, which is operating in a first state mode, has switched from a first use case to a second use case for accessing a property of an object associated with a server. The first state mode during the first use case reduces messaging in the client-server system as compared to using a second state mode. A determination is performed as to whether using the second state mode during the second use case would reduce messaging in the system as compared to using the first state mode. The client-server system is transitioned to the second state mode, if operating in the second state mode would reduce messaging in the client-server system as compared to operating in the first state mode for the second use case.