Dynamic Patch Target Calculation via HTTP Headers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for calculating a patch target in HTTP requests are inflexible, failing when URI paths return mismatched object types, lack corresponding GET operations, or include sub-resource locators, limiting user flexibility and error handling.

Innovation Solution

Incorporating additional headers in HTTP requests with patch-target method and path, querying micro-profile configurations if headers are missing, and using default values to calculate the patch target object, allowing for flexible patch target location and improved error handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a fixed pattern method is used to calculate the patch target from the URI, then the implementation is simple, but the flexibility is limited and errors occur when URI paths return mismatched object types or include sub-resource locators

Engineering Contradiction:
Improveflexibility in patch target calculationVSAvoidcomplexity of patch target calculation method
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patch target calculation method transitions from a static fixed pattern to a dynamic approach that can adapt to different scenarios. The system now supports multiple calculation methods (fixed pattern, header-based, configuration-based) that can be selected and configured dynamically based on the specific requirements and context of each patch request.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The invention introduces new parameters (patch-target-method and patch-target-path headers, micro-profile configuration parameters) that allow the patch target calculation to be customized. By changing these parameters, the system can adapt to different URI structures and object types, resolving the inflexibility of the conventional fixed pattern method.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If additional headers and configuration queries are added to enable flexible patch target location, then user flexibility and error handling are improved, but request processing complexity increases

Engineering Contradiction:
Improveerror handling capabilityVSAvoidrequest processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by checking for the presence of patch-target-method and patch-target-path headers before processing the patch request. If these headers are present, the system uses them directly; otherwise, it queries the micro-profile configuration in advance to determine the appropriate calculation method. This preliminary checking and preparation reduces errors by ensuring the correct method is selected before attempting patch target calculation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention introduces an intermediary layer (the patch-target-method and patch-target-path headers, along with micro-profile configuration) that mediates between the URI and the patch target object. This intermediary provides additional information and control mechanisms that improve error handling and flexibility without significantly increasing the overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If the patch target is calculated using a rigid fixed pattern, then processing is straightforward, but processing time increases when errors occur requiring fallback methods

Engineering Contradiction:
Improvepatch application speedVSAvoidtime for error handling and fallback
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary validation and method selection before attempting patch target calculation. By checking for the presence and validity of patch-target-method and patch-target-path headers in advance, and by pre-configuring fallback methods in the micro-profile configuration, the system avoids time-consuming error handling and fallback operations during actual patch application.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention prepares fallback mechanisms in advance by configuring multiple methods in the micro-profile configuration. If the primary method (using headers) fails or is not available, the system can immediately switch to alternative methods without significant delay. This prior preparation cushions against potential errors and maintains high productivity.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11436004B2Calculating a patch target on an application server
Publication Date: 2022.09.06 RED HAT INC
  • US11436004B2 patent drawing
  • US11436004B2 patent drawing
  • US11436004B2 patent drawing

AI summary

A method includes receiving, at an application server, a request to modify a target object, such as a resource object. The method further includes identifying, from the request, a first parameter and a second parameter and assigning the first parameter to a first variable and the second parameter to a second variable. The method then executes an operation to calculate the target object in view of the first and second variables.