Server Request Object with Embedded Recovery Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In network environments, servers often encounter exceptions while processing client requests, leading to undesirable results that require further contact with the client for resolution, which is inefficient and undesirable.
Innovation Solution
A method and system for a server computer system to receive a request object containing an exception criterion and a recovery operation, allowing the server to autonomously resolve exceptions by applying the recovery operation without additional client interaction, utilizing a resource management system in a shared computing environment to manage resource requests and allocations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server contacts the client for instructions upon exception or undesirable results, then the client can provide further instructions, but the processing time and number of interactions increase
Solution Approach 1:
The patent applies preliminary action by including recovery operations in the original request object sent from client to server. These recovery operations are prepared in advance and stored with the request, allowing the server to immediately execute them when exceptions occur without needing to contact the client again. This pre-preparation of recovery mechanisms resolves the contradiction by maintaining reliable exception handling while eliminating time-consuming back-and-forth communications.
Solution Approach 2:
The patent implements self-service by enabling the server to autonomously handle exceptions using recovery operations that were provided by the client in the original request. The server acts as its own problem-solver by executing these pre-defined recovery operations locally without requiring client intervention. This self-service capability maintains system reliability while significantly reducing processing time by eliminating the need for additional client-server interactions during exception handling.
2Productivity
If the server executes additional operations to resolve exceptions autonomously, then fewer client contacts are needed, but the server complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the exception handling responsibility into two distinct parts: the client segments the definition of recovery operations (creating them in advance), while the server segments the execution of these operations (running them when needed). The request object itself is segmented to include both the original request and the recovery operations as separate but integrated components. This segmentation allows the server to gain productivity through autonomous exception handling without bearing the full complexity of creating and managing recovery strategies.
Solution Approach 2:
The patent uses the request object as an intermediary that carries recovery operations from the client to the server. Instead of the server directly creating complex exception handling logic, the request object serves as a mediator that transports pre-defined recovery operations. This intermediary approach allows the server to execute additional operations for autonomous exception resolution while keeping server complexity manageable by relying on the structured information provided through the request object intermediary.
3Extent of automation
If the server applies recovery operations from the request object, then exception resolution is automated, but the request object structure becomes more complex
Solution Approach 1:
The patent applies merging by combining the original request and the recovery operations into a single unified request object structure. Instead of maintaining separate objects for requests and recovery operations, the patent integrates them, allowing the server to treat them as a cohesive unit. This merging enables full automation of exception resolution since all necessary information is contained within one object, while the complexity is managed through the unified structure rather than multiple interacting components.
Solution Approach 2:
The patent implements universality by designing the request object to serve multiple functions: it carries the original service request, contains exception handling instructions, and provides recovery operations. This multi-functional request object enables automated exception resolution without requiring separate specialized structures for each function. The universal request object structure achieves high automation while managing complexity by consolidating multiple responsibilities into a single versatile data structure that the server can process uniformly.
Data Source
AI summary
In an embodiment, a method of processing a request by a server computer system begins with a step of receiving an object. The object comprises the request, an exception criterion, and a recovery operation. The method continues with a step of determining that the server computer system is unable to fulfill the request due to an exception which meets the exception criterion. The method concludes with a step of applying the recovery operation to resolve the exception. In an embodiment, the server computer system comprises a resource management system for a shared computing environment and the object comprises a resource request object. The resource request object comprises a resource request, the exception criteria, and the recovery operation. The resource request indicates resources requested from the shared computing environment by a start time and for a time period.


