Dynamic API Binding Creation via Server Description Transmission

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The frequent updates to application programming interfaces (APIs) on server systems require constant maintenance and dependency management to ensure client systems can access the latest functionality, leading to significant overhead in updating bindings across multiple client systems.

Innovation Solution

A binding creation mechanism where the server system transmits an API description to the client system upon connection, allowing the client to dynamically build and update the binding, using checksums to determine if a new API description is needed, and configuring virtual machines based on the provided API information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If bindings are manually updated across multiple client systems to reflect frequent API changes on server systems, then client systems can access updated server functionality, but maintenance overhead and time consumption increase significantly

Engineering Contradiction:

Improveaccess to updated server functionalityVSAvoidmaintenance overhead

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The client system automatically detects API changes by comparing checksums and generates updated bindings without human intervention. The system self-updates by downloading new API descriptions, computing checksums, and regenerating bindings autonomously, eliminating the need for manual maintenance across multiple client systems.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements a feedback mechanism where the client system periodically checks for API changes by comparing checksums of stored API descriptions with newly received ones. When changes are detected, the system automatically triggers binding regeneration and updates, creating a closed-loop system that responds to API changes dynamically.

Inventive Principle:

Principle #23Feedback

2Adaptability or versatility

If bindings are updated frequently to match server API changes, then functionality remains current, but the complexity of managing dependencies across client systems increases

Engineering Contradiction:

Improvefunctionality currencyVSAvoiddependency management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the binding generation logic from manual processes and embeds it directly into the client system. The client system now contains the capability to automatically generate bindings locally based on received API descriptions, removing the complexity of external dependency management and manual update procedures.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by storing API descriptions and their checksums in advance. When API changes occur, the client system already has the baseline data needed to compute differences and generate updated bindings immediately, reducing the complexity of real-time dependency management.

Inventive Principle:

Principle #10Preliminary action

3Stability of the object's composition

If manual binding updates are performed across multiple client systems, then binding consistency can be maintained, but the productivity of the system decreases due to repetitive maintenance tasks

Engineering Contradiction:

Improvebinding consistencyVSAvoidsystem efficiency

Core Design Contradiction:

Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent implements a copying mechanism where the client system receives API descriptions from the server and automatically generates local copies of bindings based on these descriptions. This automated copying process ensures consistency across all client systems without requiring manual intervention, maintaining binding integrity while eliminating repetitive maintenance tasks.

Inventive Principle:

Principle #26Copying

4Loss of time

If API descriptions are transmitted to client systems for dynamic binding creation, then maintenance overhead is reduced, but network bandwidth and communication overhead increase

Engineering Contradiction:

Improvemaintenance timeVSAvoidnetwork bandwidth consumption

Core Design Contradiction:

Loss of timeVSLoss of energy

Solution Approach 1:

The system transmits only the necessary API description data and checksums to client systems, rather than complete binding files. This partial transmission approach reduces network bandwidth consumption while still enabling clients to generate bindings locally, balancing maintenance reduction with network resource usage.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS10200507B2Creation of a binding based on a description associated with a server

Publication Date: 2019.02.05 RED HAT INC

AI summary

An indication of an update to a server system may be received. In response to receiving the indication that the server system has been updated, a description associated with resources of the server system may be received. One or more functions associated with the resources of the server system from the received description may be identified where the one or more functions are associated with accessing the resources of the server system. A binding may be created for a client system in view of the indication that the server system has been updated and the identified one or more functions associated with the resources of the server system to map the one or more functions of the server system to another function of the client system.